Sparc Spec

This is phase one of the SPARC methodology, the requirements gathering step before you write any code. It walks you through extracting functional and non-functional requirements, writing Given/When/Then acceptance criteria, documenting constraints like performance and security limits, and mapping edge cases. Everything gets stored in memory using the claude-flow MCP server so later phases can reference it. The output is a structured spec document with sections for requirements, acceptance criteria, constraints, and integration points. If you're the type who jumps straight to coding and regrets it later, this forces you to think through what success looks like first. Works best when you actually have a complex feature that needs planning, not for trivial changes.