dev-implementation

1# Dev Implementation
2 
3Run implementation work for configured AI docs features. Before changing docs or code, 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 requirements, design, planning, implementation, and testing docs before changes.
104. Use the `tdd` skill while executing implementation tasks: write a failing test before production code, then make it pass.
115. Apply the `verify` skill before completing tasks or making implementation alignment claims.
126. Keep testing and implementation docs in lockstep with code. Do not defer all doc updates to final verification.
137. If parent `dev-lifecycle` established usable task tracing, emit phase, progress, next-step, blocker, and evidence events per `task`.
14 
15## Execute Plan
16 
17Use for Phase 5.
18 
191. Run `npx ai-devkit@latest lint --feature <name>` and work through the planning doc path it validates. If manual path resolution is unavoidable, first resolve `.ai-devkit.json` `paths.docs`, falling back to `docs/ai`.
202. Gather context: feature name, planning doc path, supporting docs, current branch, and current diff.
213. Parse task lists and build an ordered queue by section.
224. Present the task queue with status: `todo`, `in-progress`, `done`, `blocked`.
23…