create-spec

To turn a feature description into a formal specification, provide your plain text description to automatically generate a structured spec document and validation checklist. It enforces template structure and outputs testable, measurable requirements.

You create a requirements checklist by parsing a feature description, which automatically generates a corresponding validation checklist file. This checklist captures functional requirements and success criteria to validate during planning.

The best way to document assumptions and success criteria is to generate a ready-to-plan specification that explicitly includes these sections. It enforces documenting all assumptions and ensures success criteria are measurable.

Yes, generating a feature spec removes implementation details to keep requirements technology-agnostic. It parses the feature description and outputs only functional requirements, user scenarios, and key entities without technical specifics.

To handle ambiguity when writing feature requirements, the specification process validates the description and surfaces critical clarifications. It caps the number of questions asked to resolve ambiguity before finalizing the spec.

The generated specification and checklist files are stored in a scratchpad directory at .agents/scratchpad/<feature-name>/, containing the spec.md file and a checklists/requirements.md file structure.