Sparc Methodology

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

ruvnet 29582d5 2 files · 4.5 KB Updated

File contents

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

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

Architecture Phase

Design system structure

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: ruvnet/ruflov3/@claude-flow/codex/.agents/skills/sparc-methodology/SKILL.md

ruvnet/ruflo commit 29582d5c7a

Frequently asked questions

npx skillmds@latest add ruvnet/sparc-methodology