skills/aidd-observability/SKILL.md
Owns shared observability/runtime reporting for diagnostics, inventory, identifiers, logs, and DAG export. Use when deterministic diagnostics or inventory exports are required. Do not use when request scope is `status` stage summaries or `aidd-core` runtime ownership mapping.
npx skillsauth add grinrus/ai_driven_dev aidd-observabilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
feature-dev-aidd:aidd-flow-state, and feature-dev-aidd:aidd-loop.python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/doctor.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/tools_inventory.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/tests_log.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/dag_export.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/identifiers.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/doctor.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-observability/runtime/tools_inventory.pyskills/aidd-observability/runtime/*.skills/aidd-observability/runtime/* as canonical command paths.tools
Derives or refines tasklist items from PRD and plan artifacts. Use when tasklist stage prepares implementation-ready work items. Do not use when the request is plan authoring in `plan-new` or loop execution in `implement`.
testing
Generates consolidated ticket status summary and key artifact pointers. Use when checking current stage state or handoff readiness. Do not use when the request is diagnostics/inventory from `aidd-observability` or flow-state mutation via `aidd-flow-state`.
testing
Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. Do not use when the request is readiness gating in `review-spec` or task derivation in `tasks-new`.
testing
Runs review-stage validation for scope changes, findings, and follow-up task derivation. Use when review stage needs verdict and handoff tasks. Do not use when the request is direct implementation execution in `implement` or QA validation in `qa`.