Sparc Methodology

ruvnet/ruflo/.agents/skills/sparc-methodology

by ruvnet6051f6702b61No license74K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

AI-generated overview

Guides complex software implementations through the SPARC phases: Specification, Pseudocode, Architecture, Refinement, Completion.

What it does
This skill applies a structured SPARC workflow to complex software implementations, walking through Specification, Pseudocode, Architecture, Refinement and Completion phases. It provides phase commands routed through the @claude-flow/cli tool, a coordinator agent spawn, and two helper scripts for initializing a workflow and running a phase review checklist. It also points to reference documents covering the methodology and phase templates.
When to use it
Use it for new feature implementation, complex implementations, architectural changes, system redesign, integration work, or unclear requirements. Skip it for simple bug fixes, documentation updates, configuration changes, well-defined small tasks and routine maintenance.
Requirements
Requires the npx command and the @claude-flow/cli package, which is invoked over the network unless cached; it ships two executable shell scripts (sparc-init.sh and sparc-review.sh).

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-flow/cli hooks route --task "architecture: [design]"

Example:

bash
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

bash
npx @claude-flow/cli hooks route --task "refinement: [feedback]"

Example:

bash
npx @claude-flow/cli hooks route --task "refinement: add rate limiting and brute force protection"

Completion Phase

Finalize implementation with tests and documentation

bash
npx @claude-flow/cli hooks route --task "completion: [final checks]"

Example:

bash
npx @claude-flow/cli hooks route --task "completion: verify all tests pass, update API docs, security review"

SPARC Coordinator

Spawn SPARC coordinator agent

bash
npx @claude-flow/cli agent spawn --type sparc-coord --name sparc-lead

Scripts

ScriptPathDescription
sparc-init.agents/scripts/sparc-init.shInitialize SPARC workflow for a new feature
sparc-review.agents/scripts/sparc-review.shRun SPARC phase review checklist

References

DocumentPathDescription
SPARC Overviewdocs/sparc.mdComplete SPARC methodology guide
Phase Templatesdocs/sparc-templates.mdTemplates 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

Source and attribution

Source:ruvnet/rufloin.agents/skills/sparc-methodologyat commit6051f67

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal