
Sparc Methodology
- 112 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/claude-flow
Use sparc-methodology for development tasks
About
sparc-methodology: A skill for development. This provides functionality for development workflows.
- sparc-methodology
Sparc Methodology by the numbers
- 112 all-time installs (skills.sh)
- Ranked #2,921 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/claude-flow --skill sparc-methodologyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 112 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/claude-flow ↗ |
What it does
Use sparc-methodology for development tasks
Files
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
npx @claude-flow/cli hooks route --task "specification: [requirements]"Example:
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
npx @claude-flow/cli hooks route --task "pseudocode: [feature]"Example:
npx @claude-flow/cli hooks route --task "pseudocode: OAuth2 login flow with token refresh"Architecture Phase
Design system structure, interfaces, and dependencies
npx @claude-flow/cli hooks route --task "architecture: [design]"Example:
npx @claude-flow/cli hooks route --task "architecture: auth module with service layer, repository, and API endpoints"Refinement Phase
Iterate on the design based on feedback
npx @claude-flow/cli hooks route --task "refinement: [feedback]"Example:
npx @claude-flow/cli hooks route --task "refinement: add rate limiting and brute force protection"Completion Phase
Finalize implementation with tests and documentation
npx @claude-flow/cli hooks route --task "completion: [final checks]"Example:
npx @claude-flow/cli hooks route --task "completion: verify all tests pass, update API docs, security review"SPARC Coordinator
Spawn SPARC coordinator agent
npx @claude-flow/cli agent spawn --type sparc-coord --name sparc-leadScripts
| Script | Path | Description |
|---|---|---|
sparc-init | .agents/scripts/sparc-init.sh | Initialize SPARC workflow for a new feature |
sparc-review | .agents/scripts/sparc-review.sh | Run SPARC phase review checklist |
References
| Document | Path | Description |
|---|---|---|
SPARC Overview | docs/sparc.md | Complete SPARC methodology guide |
Phase Templates | docs/sparc-templates.md | Templates for each SPARC phase |
Best Practices
1. Check memory for existing patterns before starting 2. Use hierarchical topology for coordination 3. Store successful patterns after completion 4. Document any new learnings
#!/bin/bash
# SPARC Methodology - Init Script
# Initialize SPARC workflow for a new feature
set -e
FEATURE_NAME="${1:-new-feature}"
echo "Initializing SPARC workflow for: $FEATURE_NAME"
# Create SPARC documentation directory
mkdir -p "./docs/sparc/$FEATURE_NAME"
# Create phase files
touch "./docs/sparc/$FEATURE_NAME/1-specification.md"
touch "./docs/sparc/$FEATURE_NAME/2-pseudocode.md"
touch "./docs/sparc/$FEATURE_NAME/3-architecture.md"
touch "./docs/sparc/$FEATURE_NAME/4-refinement.md"
touch "./docs/sparc/$FEATURE_NAME/5-completion.md"
echo "SPARC workflow initialized in ./docs/sparc/$FEATURE_NAME"
#!/bin/bash
# SPARC Methodology - Review Script
# Run SPARC phase review checklist
set -e
FEATURE_DIR="${1:-.}"
echo "SPARC Phase Review Checklist"
echo "============================="
for phase in specification pseudocode architecture refinement completion; do
if [ -f "$FEATURE_DIR/${phase}.md" ]; then
echo "[x] $phase - found"
else
echo "[ ] $phase - missing"
fi
done