spec-writer

Feature specs require a guided dialogue that asks 2-3 targeted clarifying questions to surface ambiguities and constraints before drafting. This ensures alignment and scope clarity by producing a structured specification with explicit requirements and decision points for review.

A feature specification should include Overview, Goals, Non-goals, User stories, Functional requirements, Open questions, and Out of scope sections. This structured format highlights explicit requirements and decision points for review-ready alignment.

Drafting functional requirements without defined scope risks misalignment. The guided clarification process asks targeted questions to establish non-goals and out-of-scope items first, ensuring the final spec maintains strict scope clarity and actionable constraints.

The best way to identify ambiguities and constraints before writing a spec is through a guided dialogue. Answering 2-3 targeted clarifying questions surfaces hidden uncertainties, allowing you to resolve decision points and define explicit functional requirements.

To handle open questions when planning a feature, consolidate them into a dedicated section of the spec. The drafting process explicitly highlights remaining uncertainties and decision points, delivering a review-ready document for stakeholder confirmation.