spec-planner

Drafting implementation-ready specs through dialogue involves identifying gaps in scope, motivation, and constraints using a structured CLARIFY → DISCOVER → DRAFT → REFINE → DONE phase flow to align stakeholders and capture acceptance criteria.

Identifying missing requirements and edge cases is best achieved through structured dialogue that forces iterative refinement, prompting for success criteria and constraints to reduce rework and ensure alignment.

To document trade-offs and open questions for a new feature spec, leverage reusable templates and reference materials like ADRs and RFCs during the DRAFT and REFINE phases to capture implementation decisions.

Yes, this spec planning approach works for capturing acceptance criteria across scenarios by applying the phase-driven workflow to align stakeholders and rigorously explore edge cases before finalizing the spec.

You need structured spec planning instead of writing requirements directly when teams must surface missing requirements, align on scope, and reduce rework by forcing structured exploration of constraints and trade-offs.

Yes, you can generate a complete spec for a lightweight onboarding flow by iterating through clarifying questions to capture key success metrics and reduce time-to-first-use, producing an implementation-ready document.