$npx -y skills add spencermarx/open-code-review --skill sparc-methodologySPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
| 1 | # SPARC Methodology - Comprehensive Development Framework |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) is a systematic development methodology integrated with Claude Flow's multi-agent orchestration capabilities. It provides 17 specialized modes for comprehensive software development, from initial research through deployment and monitoring. |
| 6 | |
| 7 | ## Table of Contents |
| 8 | |
| 9 | 1. [Core Philosophy](#core-philosophy) |
| 10 | 2. [Development Phases](#development-phases) |
| 11 | 3. [Available Modes](#available-modes) |
| 12 | 4. [Activation Methods](#activation-methods) |
| 13 | 5. [Orchestration Patterns](#orchestration-patterns) |
| 14 | 6. [TDD Workflows](#tdd-workflows) |
| 15 | 7. [Best Practices](#best-practices) |
| 16 | 8. [Integration Examples](#integration-examples) |
| 17 | 9. [Common Workflows](#common-workflows) |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## Core Philosophy |
| 22 | |
| 23 | SPARC methodology emphasizes: |
| 24 | |
| 25 | - **Systematic Approach**: Structured phases from specification to completion |
| 26 | - **Test-Driven Development**: Tests written before implementation |
| 27 | - **Parallel Execution**: Concurrent agent coordination for 2.8-4.4x speed improvements |
| 28 | - **Memory Integration**: Persistent knowledge sharing across agents and sessions |
| 29 | - **Quality First**: Comprehensive reviews, testing, and validation |
| 30 | - **Modular Design**: Clean separation of concerns with clear interfaces |
| 31 | |
| 32 | ### Key Principles |
| 33 | |
| 34 | 1. **Specification Before Code**: Define requirements and constraints clearly |
| 35 | 2. **Design Before Implementation**: Plan architecture and components |
| 36 | 3. **Tests Before Features**: Write failing tests, then make them pass |
| 37 | 4. **Review Everything**: Code quality, security, and performance checks |
| 38 | 5. **Document Continuously**: Maintain current documentation throughout |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Development Phases |
| 43 | |
| 44 | ### Phase 1: Specification |
| 45 | **Goal**: Define requirements, constraints, and success criteria |
| 46 | |
| 47 | - Requirements analysis |
| 48 | - User story mapping |
| 49 | - Constraint identification |
| 50 | - Success metrics definition |
| 51 | - Pseudocode planning |
| 52 | |
| 53 | **Key Modes**: `researcher`, `analyzer`, `memory-manager` |
| 54 | |
| 55 | ### Phase 2: Architecture |
| 56 | **Goal**: Design system structure and component interfaces |
| 57 | |
| 58 | - System architecture design |
| 59 | - Component interface definition |
| 60 | - Database schema planning |
| 61 | - API contract specification |
| 62 | - Infrastructure planning |
| 63 | |
| 64 | **Key Modes**: `architect`, `designer`, `orchestrator` |
| 65 | |
| 66 | ### Phase 3: Refinement (TDD Implementation) |
| 67 | **Goal**: Implement features with test-first approach |
| 68 | |
| 69 | - Write failing tests |
| 70 | - Implement minimum viable code |
| 71 | - Make tests pass |
| 72 | - Refactor for quality |
| 73 | - Iterate until complete |
| 74 | |
| 75 | **Key Modes**: `tdd`, `coder`, `tester` |
| 76 | |
| 77 | ### Phase 4: Review |
| 78 | **Goal**: Ensure code quality, security, and performance |
| 79 | |
| 80 | - Code quality assessment |
| 81 | - Security vulnerability scanning |
| 82 | - Performance profiling |
| 83 | - Best practices validation |
| 84 | - Documentation review |
| 85 | |
| 86 | **Key Modes**: `reviewer`, `optimizer`, `debugger` |
| 87 | |
| 88 | ### Phase 5: Completion |
| 89 | **Goal**: Integration, deployment, and monitoring |
| 90 | |
| 91 | - System integration |
| 92 | - Deployment automation |
| 93 | - Monitoring setup |
| 94 | - Documentation finalization |
| 95 | - Knowledge capture |
| 96 | |
| 97 | **Key Modes**: `workflow-manager`, `documenter`, `memory-manager` |
| 98 | |
| 99 | --- |
| 100 | |
| 101 | ## Available Modes |
| 102 | |
| 103 | ### Core Orchestration Modes |
| 104 | |
| 105 | #### `orchestrator` |
| 106 | Multi-agent task orchestration with TodoWrite/Task/Memory coordination. |
| 107 | |
| 108 | **Capabilities**: |
| 109 | - Task decomposition into manageable units |
| 110 | - Agent coordination and resource allocation |
| 111 | - Progress tracking and result synthesis |
| 112 | - Adaptive strategy selection |
| 113 | - Cross-agent communication |
| 114 | |
| 115 | **Usage**: |
| 116 | ```javascript |
| 117 | mcp__claude-flow__sparc_mode { |
| 118 | mode: "orchestrator", |
| 119 | task_description: "coordinate feature development", |
| 120 | options: { parallel: true, monitor: true } |
| 121 | } |
| 122 | ``` |
| 123 | |
| 124 | #### `swarm-coordinator` |
| 125 | Specialized swarm management for complex multi-agent workflows. |
| 126 | |
| 127 | **Capabilities**: |
| 128 | - Topology optimization (mesh, hierarchical, ring, star) |
| 129 | - Agent lifecycle management |
| 130 | - Dynamic scaling based on workload |
| 131 | - Fault tolerance and recovery |
| 132 | - Performance monitoring |
| 133 | |
| 134 | #### `workflow-manager` |
| 135 | Process automation and workflow orchestration. |
| 136 | |
| 137 | **Capabilities**: |
| 138 | - Workflow definition and execution |
| 139 | - Event-driven triggers |
| 140 | - Sequential and parallel pipelines |
| 141 | - State management |
| 142 | - Error handling and retry logic |
| 143 | |
| 144 | #### `batch-executor` |
| 145 | Parallel task execution for high-throughput operations. |
| 146 | |
| 147 | **Capabilities**: |
| 148 | - Concurrent file operations |
| 149 | - Batch processing optimization |
| 150 | - Resource pooling |
| 151 | - Load balancing |
| 152 | - Progress aggregation |
| 153 | |
| 154 | --- |
| 155 | |
| 156 | ### Development Modes |
| 157 | |
| 158 | #### `coder` |
| 159 | Autonomous code generation with batch file operations. |
| 160 | |
| 161 | **Capabilities**: |
| 162 | - Feature implementation |
| 163 | - Code refactoring |
| 164 | - Bug fixes and patches |
| 165 | - API development |
| 166 | - Algorithm implementation |
| 167 | |
| 168 | **Quality Standards**: |
| 169 | - ES2022+ standards |
| 170 | - TypeScript type safety |
| 171 | - Comprehensive err |