Specification Synthesis
Convert tickets, feature requests, or informal requirements into a structured specification document.
Process
- •Extract the core problem being solved
- •List functional requirements (what the system must do)
- •List non-functional requirements (performance, security, UX)
- •Define clear acceptance criteria
- •Identify edge cases and constraints
Output
Create spec.md using the template in templates/spec.md.
Tips
- •Use numbered requirements for traceability
- •Each requirement should be testable
- •Distinguish must-have from nice-to-have
- •Ask clarifying questions before assuming
- •Reference existing patterns in the codebase