spec-creation

Implementation specs with acceptance criteria organize requirements into testable conditions. Use the mandatory SPEC template with sections for Summary, User Story, Acceptance Criteria, Pattern References, Success Validation, and Demo Script to ensure each criterion is measurable and verifiable before development begins.

Break user stories into technical specs by applying the SPEC template: define acceptance criteria as testable conditions, reference existing patterns for implementation guidance, attach demo scripts for validation, and map logical commits to output locations. This creates traceability from business requirements to runnable code.

Pattern references connect specs to existing implementations. Include a dedicated Pattern References section in your SPEC that links to proven solutions within your codebase or architecture library, enabling engineers to follow established approaches and reducing design ambiguity.

Yes. Demo scripts provide runnable validation commands that verify acceptance criteria are met. Include executable commands in your SPEC's Demo Script section that engineers can run during development and QA to confirm the implementation satisfies all testable requirements.

A complete technical spec includes Summary, User Story, testable Acceptance Criteria, Pattern References to existing solutions, Success Validation steps, runnable Demo Script, Logical Commits timeline, and Output Locations. This structure ensures developers have all context needed to implement and validate work.