Sparc Methodology

ruvnet/ruflo/v3/@claude-flow/codex/.agents/skills/sparc-methodology

by ruvnet5f709e36799274be6bb68fff69090bdbc8621220No license74K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion). Use when: new features, complex implementations, architectural changes. Skip when: simple fixes, documentation, configuration.

Instructions onlySoftware Development
AI-generated overview

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

What it does
This skill provides a structured development workflow built on the SPARC phases: Specification, Pseudocode, Architecture, Refinement and Completion. It states when to trigger the workflow (new features, complex implementations, architectural changes) and when to skip it (simple fixes, documentation, configuration), and lists commands for routing specification and architecture tasks through a CLI. It also lists best practices such as checking memory for existing patterns, using hierarchical topology for coordination, storing successful patterns, and documenting learnings.
When to use it
Use it when starting new features, complex implementations or architectural changes that benefit from a phased plan. Skip it for simple fixes, documentation or configuration work.
Requirements
No scripts ship with the skill; it is instructions only. The listed commands invoke the external @claude-flow/cli package through npx, which requires Node.js and network access to fetch the package.

Sparc Methodology Skill

Purpose

SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).

When to Trigger

  • new features
  • complex implementations
  • architectural changes

When to Skip

  • simple fixes
  • documentation
  • configuration

Commands

Specification Phase

Define requirements and acceptance criteria

bash
npx @claude-flow/cli hooks route --task "specification: [requirements]"

Architecture Phase

Design system structure

bash
npx @claude-flow/cli hooks route --task "architecture: [design]"

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/rufloinv3/@claude-flow/codex/.agents/skills/sparc-methodologyat commit5f709e3

License: No license

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

Report or request removal