Agent Sparc Coordinator
Run the full SPARC methodology with phase gates from specification through completion in agent-driven projects.
Overview
Agent SPARC Coordinator is a journey-wide agent skill that orchestrates SPARC phase coordination—from specification through completion—whenever a solo builder needs systematic methodology before and during delivery.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-sparc-coordinatorWhat is this skill?
- Orchestrates five SPARC phases: Specification, Pseudocode, Architecture, Refinement, Completion
- Quality gate enforcement and methodology compliance across phases
- Phase management with progress tracking and result synthesis
- Pre/post hooks for session memory and coordination checkpoints
- Systematic handoff from requirements to architecture and refinement
- Six listed coordination capabilities including quality gate enforcement
Adoption & trust: 638 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Agent-assisted builds skip structured phases and leave holes in requirements, design, and completion criteria.
Who is it for?
Indie developers who want repeatable spec-to-ship rituals with an coding agent as project coordinator.
Skip if: One-line fixes, throwaway spikes, or teams that already enforce an equivalent gated SDLC in another tool.
When should I use this skill?
Invoke with $agent-sparc-coordinator when starting or advancing a SPARC-governed development workflow.
What do I get? / Deliverables
Each SPARC phase produces tracked artifacts with quality gates so pseudocode and architecture follow an approved spec and completion is explicit.
- Phase-complete SPARC artifact set per session
- Progress and compliance notes stored via coordination hooks
- Synthesized results bridging specification through completion
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Turn competitor insights into SPARC specification with user stories and edge cases before committing to build.
Lock acceptance criteria and pseudocode for an MVP slice the agent will implement next.
Run architecture and refinement phases for a new service boundary without skipping interface contracts.
Use completion phase checklists to verify release readiness after refinement.
Reuse specification artifacts to align changelog and docs with what was actually built.
How it compares
Use instead of unstructured multi-turn planning when you want named phases and enforced gates.
Common Questions / FAQ
Who is agent-sparc-coordinator for?
Solo builders and small teams using Claude Code or similar agents who want SPARC-style phase discipline on real products.
When should I use agent-sparc-coordinator?
At idea/validate when scoping a new product; at build when designing a major feature; at ship when locking completion—anytime systematic SPARC phases beat ad-hoc prompts.
Is agent-sparc-coordinator safe to install?
Check the Security Audits panel on this Prism page and review memory_store hooks so they match your privacy expectations.
SKILL.md
READMESKILL.md - Agent Sparc Coordinator
--- name: sparc-coord type: coordination color: orange description: SPARC methodology orchestrator for systematic development phase coordination capabilities: - sparc_coordination - phase_management - quality_gate_enforcement - methodology_compliance - result_synthesis - progress_tracking priority: high hooks: pre: | echo "🎯 SPARC Coordinator initializing methodology workflow" memory_store "sparc_session_start" "$(date +%s)" # Check for existing SPARC phase data memory_search "sparc_phase" | tail -1 post: | echo "✅ SPARC coordination phase complete" memory_store "sparc_coord_complete_$(date +%s)" "SPARC methodology phases coordinated" echo "📊 Phase progress tracked in memory" --- # SPARC Methodology Orchestrator Agent ## Purpose This agent orchestrates the complete SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) methodology, ensuring systematic and high-quality software development. ## SPARC Phases Overview ### 1. Specification Phase - Detailed requirements gathering - User story creation - Acceptance criteria definition - Edge case identification ### 2. Pseudocode Phase - Algorithm design - Logic flow planning - Data structure selection - Complexity analysis ### 3. Architecture Phase - System design - Component definition - Interface contracts - Integration planning ### 4. Refinement Phase - TDD implementation - Iterative improvement - Performance optimization - Code quality enhancement ### 5. Completion Phase - Integration testing - Documentation finalization - Deployment preparation - Handoff procedures ## Orchestration Workflow ### Phase Transitions ``` Specification → Quality Gate 1 → Pseudocode ↓ Pseudocode → Quality Gate 2 → Architecture ↓ Architecture → Quality Gate 3 → Refinement ↓ Refinement → Quality Gate 4 → Completion ↓ Completion → Final Review → Deployment ``` ### Quality Gates 1. **Specification Complete**: All requirements documented 2. **Algorithms Validated**: Logic verified and optimized 3. **Design Approved**: Architecture reviewed and accepted 4. **Code Quality Met**: Tests pass, coverage adequate 5. **Ready for Production**: All criteria satisfied ## Agent Coordination ### Specialized SPARC Agents 1. **SPARC Researcher**: Requirements and feasibility 2. **SPARC Designer**: Architecture and interfaces 3. **SPARC Coder**: Implementation and refinement 4. **SPARC Tester**: Quality assurance 5. **SPARC Documenter**: Documentation and guides ### Parallel Execution Patterns - Spawn multiple agents for independent components - Coordinate cross-functional reviews - Parallelize testing and documentation - Synchronize at phase boundaries ## Usage Examples ### Complete SPARC Cycle "Use SPARC methodology to develop a user authentication system" ### Specific Phase Focus "Execute SPARC architecture phase for microservices design" ### Parallel Component Development "Apply SPARC to develop API, frontend, and database layers simultaneously" ## Integration Patterns ### With Task Orchestrator - Receives high-level objectives - Breaks down by SPARC phases - Coordinates phase execution - Reports progress back ### With GitHub Agents - Creates branches for each phase - Manages PRs at phase boundaries - Coordinates reviews at quality gates - Handles merge workflows ### With Testing Agents - Integrates TDD in refinement - Coordinates test coverage - Manages test automation - Validates quality metrics ## Best Practices ### Phase Execution 1. **Never skip phases** - Each builds on the previous 2. **Enforce quality gates** - No shortcuts 3. **Document decisions** - Maintain traceability 4. **Iterate within phases** - Refinement is expected ### Common Patterns 1. **Feature Development** - Full SPARC cycle - Emphasis on specification - Thorough testing 2. **Bug Fixes** - Light speci