Verified:GitHub

sparc-methodology

Implement a structured development lifecycle with Specification, Pseudocode, Architecture, Refinement, and Completion phases.

Updated Dec 12, 2025

Search Tags:#workflow #planning #development #architecture #methodology #sparc

Ready to run

npx skills add https://github.com/MichelMokbel/RMS-1 --skill sparc-methodology-michelmokbel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sparc-methodology
Source: https://github.com/MichelMokbel/RMS-1/tree/main/.agents/skills/sparc-methodology
Command: npx skills add https://github.com/MichelMokbel/RMS-1 --skill sparc-methodology-michelmokbel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the lack of structure in complex software development by enforcing a rigorous, multi-phase planning process that prevents architectural drift and requirement ambiguity.

Core Features & Use Cases

Phase-Based Workflow: Guides development through Specification, Pseudocode, Architecture, Refinement, and Completion phases.
Standardized Documentation: Automatically initializes project-specific documentation directories and tracking files.
Use Case: Use this when starting a major architectural redesign or a complex new feature to ensure all requirements are documented and validated before writing production code.

Quick Start

Initialize the SPARC workflow for your new feature by running the sparc-init script with your feature name as an argument.

Frequently Asked Questions about sparc-methodology

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

FAQPage Schema

What is a structured methodology for complex software development workflows?▼

A structured development methodology enforces rigorous planning across Specification, Pseudocode, Architecture, Refinement, and Completion phases to prevent architectural drift and requirement ambiguity in complex software projects.

How do I plan a major architectural redesign to avoid requirement ambiguity?▼

To plan an architectural redesign, use a multi-phase workflow that validates requirements and standardizes documentation before writing production code, ensuring consistent architectural oversight throughout the software development lifecycle.

When do I need a multi-phase planning process for feature implementation?▼

You need a multi-phase planning process when starting complex new features or system redesigns where strict requirement validation, architectural documentation, and pseudocode refinement are required before implementation.

Can I initialize standardized documentation directories for my software development workflow?▼

Yes, you can initialize project-specific documentation directories and tracking files automatically by running the initialization script with your feature name as an argument to set up the structured workflow.

Does a phase-based development workflow work for complex feature redesigns?▼

Yes, a phase-based development workflow handles complex feature redesigns by guiding teams through structured specification, pseudocode generation, architecture planning, and refinement stages before final code completion.

What are the limitations of enforcing rigorous planning standards in software architecture?▼

Enforcing rigorous planning standards introduces overhead through mandatory documentation and sequential phase validation, making it less suitable for rapid prototyping or minor updates that do not require comprehensive architectural oversight.