spec-feature

To turn a feature idea into a testable specification, you must clarify what the feature does, who it is for, and how users interact with it, then document these requirements in a standardized spec file.

The PREFIX-NNN convention is a standardized ID format used within design/specs/*.md files to organize and track feature requirements, ensuring every specification has a unique, traceable identifier for verification workflows.

You structure user stories and epic scoping by defining the what, who, why, and how of a feature in a formal spec file, creating a clear iterative workflow from ideation to specification before implementation begins.

Yes, you can use automated tests to verify feature design specs. The spec-test approach supports an iterative workflow where specifications defined in your markdown files are directly tied to verification workflows.

Yes, you need to create or update design/specs/{domain}.md files to store your feature specifications. This standardized directory structure ensures requirements are properly formatted and accessible for iterative verification.

You should write a design spec before development when planning a feature from idea to implementation, as this reduces ambiguity and rework by enforcing clear, testable requirements prior to writing any code.