dev-planning

1# Dev Planning
2 
3Run planning creation and reconciliation for configured AI docs features. Before changing docs, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.
4 
5## Phase Contract
6 
71. Run `npx ai-devkit@latest lint` before phase work.
82. If working on a named feature, run `npx ai-devkit@latest lint --feature <name>`.
93. Read existing configured planning, implementation, and testing docs before changes. Resolve paths through `lint --feature` instead of assuming `docs/ai`.
104. Keep task creation and updates traceable to requirements, design, testing scenarios, completed work, blockers, or newly discovered scope.
115. If parent `dev-lifecycle` established usable task tracing, emit planning phase, progress, blocker/scope, and next-step events per `task`.
12 
13## Create Initial Plan
14 
15Use for Phase 4 after requirements, design, and initial testing docs exist.
16 
171. Run `npx ai-devkit@latest lint --feature <name>` and identify the planning doc path it validates. If `docs init-feature` just ran, use the returned planning path as authoritative.
182. Read requirements, design, and testing docs for the feature.
193. Convert goals, user stories, design components, API/data changes, migration needs, and testing scenarios into implementation tasks.
204. Group tasks by milestone or logical sequence.
215. For each task, include outcome, dependencies, validation evidence, and related testing scenarios.
22…