- Formalizing vague feature requests into structured requirements
- Clarifying scope boundaries for a feature area
- Establishing acceptance criteria for user stories
Key Principle
Specifications describe desired behavior from the user's perspective. They define what the system should do, not how it should be built. Business value must be explicit in every requirement.
Process
- Elicit requirements - Extract functional and non-functional requirements from feature description
- Write user stories - Author stories in standard format with personas
- Define acceptance criteria - Testable conditions for each story (Given/When/Then)
- Identify edge cases - Error scenarios and boundary conditions
- Clarify gaps - Surface and resolve ambiguities and contradictions
- Document assumptions - Make implicit assumptions explicit
- Define scope - Clearly delineate in-scope vs. out-of-scope
- Human review - Approve specification before planning
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-specification
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator