Dev Lifecycle

Sequential phases producing docs in docs/ai/. Flow: 1→2→3→4→(5 after each task)→6→7→8.

Early-Phase Clarification Contract

For Phases 1-3, converge on shared understanding before docs or implementation momentum:

1. List every material product, UX, architecture, scope, validation, rollout, contradiction, trade-off, or open question from the request, memory, and existing docs.
2. Ask until each item is answered, explicitly deferred, or accepted by the user as a named assumption. Do not silently infer material decisions.
3. Ask one decision at a time; include why it matters, 2-3 viable options when useful, and your recommended answer with brief rationale.
4. Do not create, update, approve, or transition past requirements/design/planning while material open questions remain.
5. Restate the shared understanding before updating docs or suggesting the next phase.

Prerequisite

Before starting any phase, run npx ai-devkit@latest lint to verify the base docs/ai/ structure exists and is valid.

If working on a specific feature, also run npx ai-devkit@latest lint --feature <name> to validate feature-scoped docs.