dev-design

1# Dev Design
2 
3Run the design review phase 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 existing requirements and design docs before changes.
104. Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
115. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
126. Do not approve or transition past design while material open questions remain.
137. Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
148. If parent `dev-lifecycle` established usable task tracing, emit design phase, progress, blocker/open-question, and next-step events per `task`.
15 
16## Review Design
17 
18Use for Phase 3.
19 
201. Run `npx ai-devkit@latest lint --feature <name>` and review the design doc path it validates. If manual path resolution is unavoidable, first resolve `.ai-devkit.json` `paths.docs`, falling back to `docs/ai`.
212. Search memory for relevant architecture patterns or past decisions.
22…