sparc-methodology
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding. Use when: new feature implementation, complex implementations, architectural changes, system redesign, integration work, unclear requirements. Skip when: simple bug fixes, documentation updates, configuration changes, well-defined small tasks, routine maintenance.
npx skills add ruvnet/ruflo --skill sparc-methodology --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 Methodology Skill ## Purpose SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding. ## When to Trigger - new feature implementation - complex implementations - architectural changes - system redesign - integration work - unclear requirements ## When to Skip - simple bug fixes - documentation updates - configuration changes - well-defined small tasks - routine maintenance ## Commands ### Specification Phase Define requirements, acceptance criteria, and constraints ```bash npx @claude-flow/cli hooks route --task "specification: [requirements]" ``` **Example:** ```bash npx @claude-flow/cli hooks route --task "specification: user authentication with OAuth2, MFA, and session management" ``` ### Pseudocode Phase Write high-level pseudocode for the implementation ```bash npx @claude-flow/cli hooks route --task "pseudocode: [feature]" ``` **Example:** ```bash npx @claude-flow/cli hooks route --task "pseudocode: OAuth2 login flow with token refresh" ``` ### Architecture Phase Design system structure, interfaces, and dependencies ```bash npx @claude-fl
- Purpose
- When to Trigger
- When to Skip
- Commands
- Specification Phase
- Pseudocode Phase
- Architecture Phase
- Refinement Phase
- Completion Phase
- SPARC Coordinator
- Scripts
- References
- Best Practices
npx @claude-flow/cli hooks route --task "specification: [requirements]" npx @claude-flow/cli hooks route --task "specification: user authentication with OAuth2, MFA, and session management" npx @claude-flow/cli hooks route --task "pseudocode: [feature]" npx @claude-flow/cli hooks route --task "pseudocode: OAuth2 login flow with token refresh" npx @claude-flow/cli hooks route --task "architecture: [design]" npx @claude-flow/cli hooks route --task "architecture: auth module with service layer, repository, and API endpoints" npx @claude-flow/cli hooks route --task "refinement: [feedback]" npx @claude-flow/cli hooks route --task "refinement: add rate limiting and brute force protection" npx @claude-flow/cli hooks route --task "completion: [final checks]" npx @claude-flow/cli hooks route --task "completion: verify all tests pass, update API docs, security review"
What does the sparc-methodology skill do?
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding. Use when: new feature implementation, complex implementations, architectural changes, system redesign, integration work, unclear requirements. Skip when: simple bug fixes, documentation updates, configuration changes, well-defined small tasks, routine maintenance.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill sparc-methodology --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.