dev-requirements

1# Dev Requirements
2 
3Run the requirements phases for configured AI docs features. Before making docs or code changes, 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. If lint fails because project docs are not initialized, run `npx ai-devkit@latest init -a -e claude --built-in --yes`, then rerun lint.
104. Read existing configured AI docs and keep diffs minimal. Do not assume `docs/ai`; it is only the default docs directory.
115. Ask until every material product, UX, architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
126. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
137. Do not create, update, approve, or transition past requirements while material open questions remain.
148. Restate the shared understanding before updating docs or suggesting the next phase.
159. If parent `dev-lifecycle` established usable task tracing, emit requirements phase, clarification/progress, blocker/open-question, and next-step events per `task`.
16 
17## New Requirement
18 
19Use for Phase 1 or `/new-requirement`.
20…