feature-dev-aidd

Analyze the initial idea, draft the PRD, and prepare only the missing user questions needed to continue.

Implement the next scoped work item in loop mode with bounded evidence and controlled validation.

Review the implementation plan for executability, risk, and test strategy before the PRD review pass.

Draft the implementation plan from PRD and research artifacts, keeping it execution-ready and bounded.

Review the PRD for completeness, risks, and metrics after the plan review pass.

Run the final QA verification for the current loop scope and report severity plus PRD traceability.

Analyze the codebase for integration points, reuse, and risks, then update the research report for the ticket.

Review the current loop-scope changes for risks, blockers, and follow-up work without drifting into refactoring.

Expand the tasklist into implementation-ready iterations without running an interview flow.

Review plan executability against PRD and research artifacts and return the final validation gaps without editing the plan.

Aggregates shared runtime navigation and cross-skill ownership links. Use when resolving shared runtime entrypoints or ownership boundaries. Do not use when the request belongs to `aidd-policy` output/question rules or `status` summary reporting.

Owns shared DocIO runtime for markdown slicing/patching, actions validation/apply, and context-map expansion. Use when stage skills need canonical DocIO operations. Do not use when the request primarily belongs to `aidd-flow-state` lifecycle updates or `aidd-core` ownership routing.

Owns shared flow/state runtime for stage state, progress/tasklist, and stage-result lifecycle. Use when orchestration needs canonical active-stage, progress, tasklist, or stage-result commands. Do not use when the request is about `aidd-docio` action patch mechanics or `status` read-only summaries.

Initializes AIDD workspace scaffolding for the current project. Use when bootstrapping canonical `aidd/` templates and project-owned test execution contract in `aidd/config/gates.json`. Do not use when the request is to start feature ideation (`idea-new`) or to inspect existing ticket progress (`status`).

Enforces loop-mode discipline for implement/review/qa (packs, scope, no questions). Use when loop stages require bounded scope and retry policy. Do not use when direct stage execution belongs to `implement`, `review`, or `qa` stage skills.

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.

Defines the shared policy contract for output format, read discipline, question format, and loop safety. Use when applying cross-stage policy rules. Do not use when the request is to execute runtime orchestration from `aidd-core` or `aidd-loop`.

Owns shared RLM evidence workflow for subagents (slice, build, verify, finalize, pack). Use when preload roles require canonical RLM evidence operations. Do not use when the request is stage-local research execution in `researcher` or stage handoff-only guidance in `aidd-stage-research`.

Defines stage-specific research contract for subagent evidence reading and handoff behavior. Use when researcher subagent stage rules are needed. Do not use when the request belongs to shared RLM runtime ownership in `aidd-rlm` or direct stage command execution in `researcher`.

Bootstraps a new feature ticket by setting active context, deriving `slug_hint`, and preparing PRD questions. Use when the idea stage starts for a new ticket. Do not use when the request is to refresh research artifacts (`researcher`) or draft implementation plans (`plan-new`).

Executes implement-stage loop workflow for the next scoped work item through stage-chain orchestration. Use when implement stage enters loop mode. Do not use when the request is focused on findings validation in `review` or verification/reporting in `qa`.

Drafts implementation plan from ready PRD and research artifacts. Use when PRD and research gates pass and plan stage should start. Do not use when the request is feature kickoff in `idea-new` or readiness approval in `review-spec`.

Runs QA-stage validation, report generation, and postflight actions for the current scope. Use when QA stage is ready for loop verification. Do not use when the request belongs to `review` findings synthesis or `implement` execution loops.

Generates or refreshes research artifacts and RLM evidence for a ticket. Use when research stage should produce or update canonical RLM outputs. Do not use when the request is initial ticket bootstrap in `idea-new` or implementation planning in `plan-new`.

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`.

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`.

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`.

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`.

16 hooks across 6 events