sparc-methodology

Coordinate software development lifecycles using SPARC phases and pseudocode refinement.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/monktui/git-review --skill sparc-methodology-monktui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparc-methodology
Source: https://github.com/monktui/git-review/tree/main/.claude/skills/sparc-methodology
Command: npx skills add https://github.com/monktui/git-review --skill sparc-methodology-monktui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPARC methodology helps you avoid scattered development by providing a structured, phase-based workflow that turns vague ideas into implemented, reviewed, and completed deliverables.

Core Features & Use Cases

  • Specification-first planning: translate requirements into clear success criteria and pseudocode to prevent wasted implementation.
  • TDD-driven refinement: build features via red-green-refactor cycles to improve correctness and maintainability.
  • Architecture + review + completion: coordinate system design decisions, run quality checks, and finalize integration with captured outcomes.
  • Use case: when you need to deliver a feature end-to-end, use SPARC to guide research, design, test-first implementation, review, and documentation in a repeatable flow.

Quick Start

Ask an AI agent to execute SPARC in order—research, architecture, TDD implementation, reviewer pass, then completion—using the mode name you prefer for each phase.

Frequently Asked Questions about sparc-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the SPARC methodology for software development?

The SPARC methodology is a structured, phase-based workflow for the software development lifecycle that coordinates specification, architecture, TDD implementation, review, and completion to turn vague ideas into reviewed deliverables.

How do I structure an end-to-end feature workflow using TDD and specification phases?

To structure an end-to-end feature workflow, execute SPARC phases in order: research, architecture, TDD-driven refinement using red-green-refactor cycles, a reviewer pass, and finally completion to produce refined, review-ready outputs.

Can I use SPARC for multi-agent orchestration and debugging?

Yes, you can use SPARC for multi-agent orchestration, debugging, and refactoring by running phase-appropriate agent roles and maintaining memory-based context across each development step.

Does the SPARC workflow require predefined modes and pseudocode?

Yes, the SPARC workflow requires defining SPARC modes and translating requirements into clear success criteria and pseudocode before implementation to prevent wasted development effort.

What is the best way to maintain context across automated software architecture phases?

The best way to maintain context across architecture phases is using memory-based context management within SPARC, ensuring consistent planning and quality gates across multi-agent orchestration.