spec-writing

Spec-driven development uses a structured five-phase process with gated approvals to capture requirements before implementation. It requires completing context gathering, specification drafting, planning, task breakdown, and implementation gating sequentially to ensure traceability and completeness.

Draft an A1-spec.md document using elicitation prompts and templates to capture requirements, then await gated approval before proceeding. This structured five-phase process ensures specifications remain testable, complete, and traceable across context gathering, drafting, planning, and task breakdown.

Yes, phase gates produce collaboration-friendly outputs designed for AI-assisted planning, reviews, and handoffs. The workflow guides both practitioners and AI agents through context gathering, specification drafting, and gated approvals to ensure alignment before implementation.

Use structured elicitation prompts and templates within a gated five-phase workflow to prevent scope drift. Requiring formal approval before moving from specification drafting to planning ensures all open questions are resolved and requirements remain fully traceable.

Specification writing without gated approvals risks scope drift and misalignment. The structured five-phase process enforces formal approval between context gathering, drafting, planning, task breakdown, and implementation to ensure completeness and traceability before development proceeds.