What problem does it solve?
Starting a feature without a clear specification leads to scope creep, missed edge cases, and rework. This Skill runs Phase 1 of the SPARC methodology, turning a rough feature description into a structured, testable specification stored in persistent memory.
Core Features & Use Cases
- Requirements Gathering: Identifies functional and non-functional requirements, integration points, and data requirements from a feature description and the existing codebase.
- Acceptance Criteria & Edge Cases: Produces at least three Given/When/Then acceptance criteria plus documented constraints and failure scenarios.
- Persistent Phase State: Stores the specification in the ruflo memory system under the sparc-phases namespace and tracks workflow state so later SPARC phases (Pseudocode, Architecture, Refinement, Completion) can build on it.
- Use Case: Before implementing a new API endpoint, run this phase to produce a specification document with testable acceptance criteria, then advance to the Pseudocode phase via the SPARC gate check.
Quick Start
Run the sparc-spec skill with a feature description such as "user authentication with OAuth" to generate and store the Phase 1 specification.