sparc-spec
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
Profile →npx skills add ruvnet/ruflo --skill sparc-spec --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SPARC Specification Phase Run Phase 1 of the SPARC methodology: define what must be built and how success is measured. ## When to use When starting a new feature or project that needs structured requirements gathering before any code is written. This phase produces the foundational specification that all subsequent phases (Pseudocode, Architecture, Refinement, Completion) build upon. ## Steps 1. **Initialize phase tracking** — call `mcp__plugin_ruflo-core_ruflo__hooks_intelligence_trajectory-start` with metadata `{ "phase": "specification", "feature": "$ARGUMENTS" }` 2. **Check for prior work** — call `mcp__plugin_ruflo-core_ruflo__memory_search` with namespace `sparc-state` and query for the feature to see if a SPARC workflow already exists. If it does, retrieve existing artifacts. If not, initialize state with phase 1. 3. **Search for similar patterns** — call `mcp__plugin_ruflo-core_ruflo__neural_predict` with the feature description to find relevant past specifications and learned patterns 4. **Gather requirements** — analyze the feature description and the codebase to identify: - **Functional requirements**: what the feature must do (user-facing behaviors) - **Non-functional
- When to use
- Steps
- Output format
What does the sparc-spec skill do?
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
How do I install it?
Run `npx skills add ruvnet/ruflo --skill sparc-spec --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.