
sparc-methodology
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement
by ruvnetFree
Description
sparc-methodology is an agent skill from the ruflo project that sets out the SPARC development workflow: Specification, Pseudocode, Architecture, Refinement and Completion. It is a structured way to approach a complex implementation so that the planning is done before the code is written. The skill says when to use it, for new features, complex implementations, architectural changes, system redesigns, integration work and unclear requirements. It also says when to skip it, for simple bug fixes, documentation updates, configuration changes, well-defined small tasks and routine maintenance, since the full method is heavier than those need. The idea is that an assistant first pins down what is needed, then designs the approach in pseudocode and the architecture, then refines the design, and finally completes and verifies the work, rather than jumping straight into code. It suits developers who have a larger change to plan and want an assistant to slow down at the start and check its reasoning as it goes. The skill is a process, so its value comes from following the steps and not from the tool itself. It passes Gen Agent Trust Hub, Socket and Snyk on skills.sh, and it has about 1,200 installs. Install it with npx skills add https://github.com/ruvnet/ruflo --skill sparc-methodology.…
Highlights
- Five phases: specification, pseudocode, architecture, refinement, completion
- Plans before code for complex implementations
- Clear guidance on when to use and when to skip it
- Suits features, redesigns and unclear requirements
Ratings & Reviews
No ratings yet
Be the first to rate sparc-methodology.
People also visit

openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact

openspec-propose
Propose a new OpenSpec change with all artifacts generated in one step

openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts
sparc-methodology FAQ
What are the phases?
Specification, pseudocode, architecture, refinement and completion.
When should I use it?
For new features, complex implementations, architectural changes, system redesigns, integration work and unclear requirements.
When should I skip it?
For simple bug fixes, documentation updates, configuration changes, small well-defined tasks and routine maintenance.
How do I install it?
Run npx skills add https://github.com/ruvnet/ruflo --skill sparc-methodology.
Which security audits does it have?
On skills.sh, Gen Agent Trust Hub, Socket and Snyk all pass.
What are the best sparc-methodology alternatives?
Popular alternatives to sparc-methodology include plan-orchestrate, pr and openspec-continue-change. See all sparc-methodology alternatives




