skills/status/SKILL.md
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`.
npx skillsauth add grinrus/ai_driven_dev statusInstall 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.
Follow feature-dev-aidd:aidd-core and feature-dev-aidd:aidd-loop.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/status/runtime/status.py --ticket <ticket> as the sole canonical status entrypoint; it may refresh index data internally when needed.python3 ${CLAUDE_PLUGIN_ROOT}/skills/status/runtime/index_sync.py --ticket <ticket> only as a manual repair or debugging path when status.py cannot recover the index on its own.status.py, including active-ticket fallback behavior and derived AIDD:ACTIONS_LOG.python3 ${CLAUDE_PLUGIN_ROOT}/skills/status/runtime/status.py--ticket <ticket> (falls back to active ticket when available).python3 ${CLAUDE_PLUGIN_ROOT}/skills/status/runtime/index_sync.pystatus.py flow.--ticket <ticket> and current workspace index sources.status.py.AIDD:ACTIONS_LOG to the most recent *.actions.json under aidd/reports/actions/<ticket>/... (use rg if needed).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
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`.
tools
Reviews plan and PRD, then gates readiness for task derivation. Use when plan and PRD artifacts are ready for downstream planning readiness. Do not use when the request is plan authoring in `plan-new` or task derivation in `tasks-new`.