spec-synthesis
Transform ambiguous requirements into precise specifications. Use before any non-trivial implementation.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
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
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-02-04
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!