sparc-methodology
Skill2 starsChanged 7 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Write high-level pseudocode for the implementation
- Distinctive: line 115
Check memory for existing patterns before starting
- Distinctive: line 116
Use hierarchical topology for coordination
- Distinctive: line 118
Document any new learnings
“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
- Check memory for existing patterns before starting
- Use hierarchical topology for coordination
- Store successful patterns after completion
- Document any new learnings
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions33 projects use a version of this.
Word for word · 5
- ruvnet/claude-flow★ 80k100% same
- ruvnet/ruflo★ 79k100% same
- fidgetcoding/fidgetflo★ 1100% same
- jpoindexter/theft-kit★ 1100% same
- Soulcynics404/AgentForge★ 1100% same
Edited · 0
None found.
Wrote their own version · 28
- ruvnet/wifi-densepose★ 102ksame name
- ruvnet/RuView★ 102ksame name
- ruvnet/RuVector★ 4.7ksame name
- ruvnet/ruvector★ 4.7ksame name
- ruvnet/agentic-flow★ 834same name
- proffesor-for-testing/agentic-qe★ 515same name
- ruvnet/ruv-FANN★ 385same name
- spencermarx/open-code-review★ 382same name
- chatman-media/timeline-studio★ 224same name
- ruvnet/midstream★ 149same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository139 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- v2/CLAUDE.mdCLAUDE.md
- v3/CLAUDE.mdCLAUDE.md
- agent-adaptive-coordinatorSkill
- agent-agentic-paymentsSkill
- agent-agentSkill
- agent-analyze-code-qualitySkill
- agent-app-storeSkill
- agent-architectureSkill
- agent-arch-system-designSkill
- agent-authenticationSkill
- agent-automation-smart-agentSkill
- agent-base-template-generatorSkill
- agent-benchmark-suiteSkill
- agent-byzantine-coordinatorSkill
- agent-challengesSkill
- agent-code-analyzerSkill
- agent-code-goal-plannerSkill
- agent-code-review-swarmSkill
- agent-coderSkill
- agent-collective-intelligence-coordinatorSkill
- agent-consensus-coordinatorSkill
- agent-coordinationSkill
- agent-coordinator-swarm-initSkill
- agent-crdt-synchronizerSkill
- agent-data-ml-modelSkill
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-dev-backend-apiSkill
- agent-docs-api-openapiSkill
- agent-github-modesSkill
- agent-github-pr-managerSkill
- agent-goal-plannerSkill
- agent-gossip-coordinatorSkill
- agent-hierarchical-coordinatorSkill
- agentic-jujutsuSkill
- agent-implementer-sparc-coderSkill
- agent-issue-trackerSkill
- agent-load-balancerSkill
- agent-matrix-optimizerSkill
- agent-memory-coordinatorSkill
- agent-mesh-coordinatorSkill
- agent-migration-planSkill
- agent-multi-repo-swarmSkill
- agent-neural-networkSkill
- agent-ops-cicd-githubSkill
- agent-orchestrator-taskSkill
- agent-pagerank-analyzerSkill
- agent-paymentsSkill
- agent-performance-analyzerSkill
- agent-performance-benchmarkerSkill
- agent-performance-monitorSkill
- agent-performance-optimizerSkill
- agent-plannerSkill
- agent-pr-managerSkill
- agent-production-validatorSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.