sparc-methodology

Solid

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

AI & Automation 56,717 stars 6459 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
39
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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

Details

Author
ruvnet
Repository
ruvnet/ruflo
Created
12 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category