spec-synthesis
Transform ambiguous requirements into precise specifications. Use before any non-trivial implementation.
When & Why to Use This Skill
The spec-synthesis skill is a specialized tool designed to bridge the gap between ambiguous user requirements and technical implementation. By automating the creation of structured specification documents, it helps development teams define functional requirements, non-functional constraints, and clear acceptance criteria, ensuring project alignment and reducing scope creep before any code is written.
Use Cases
- Requirement Refinement: Transform informal stakeholder requests or brief tickets into comprehensive technical specification documents (spec.md).
- Pre-Implementation Planning: Identify potential edge cases, security constraints, and UX requirements during the discovery phase of a new feature.
- Quality Assurance Alignment: Establish clear, testable acceptance criteria that serve as a single source of truth for both developers and QA engineers.
- Architectural Traceability: Reference existing codebase patterns and numbered requirements to ensure new features integrate seamlessly with the current system.
| name | spec-synthesis |
|---|---|
| description | Transform ambiguous requirements into precise specifications. Use before any non-trivial implementation. |
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