planner

To create implementation-ready feature specs, articulate the feature request and define the problem space, then draft a structured document including goals, acceptance criteria, tests, and success metrics. This reduces ambiguity, scope creep, and rework by validating requests before development.

A feature design document should include the problem statement, goals, acceptance criteria, tests, and success metrics. It must also review existing architecture docs and prior specifications to ensure consistency with current system design before presenting the draft for approval.

To write acceptance criteria aligned with architecture guidelines, research existing code, architecture documentation, and prior specifications first. This ensures the feature design maintains consistency and avoids writing implementation code before the spec is formally approved.

Yes, you can generate a spec draft and iterate until approval is granted. The workflow validates the initial request, consults existing documentation, drafts or updates the spec file, and presents a formatted version for review to ensure alignment before implementation begins.

Writing feature specs prevents scope creep by defining the problem space and establishing clear acceptance criteria before coding begins. Creating structured, implementation-ready documents ensures developers and stakeholders share a single source of truth, reducing ambiguity and minimizing rework.

You should not use a spec-driven planning workflow if your project requires immediate implementation code rather than documentation, or if the feature design lacks sufficient context to define clear acceptance criteria and success metrics for a formal review process.