spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: RefractSystems

Creates a structured six-element SPEC before coding to guide implementation.

Updated Aug 27, 2026

Search Tags:#planning #documentation #specification #requirements #quality #process

Ready to run

npx skills add https://github.com/RefractSystems/virtmcu --skill spec-driven-development-refractsystems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/RefractSystems/virtmcu/tree/main/.gemini/skills/spec-driven-development
Command: npx skills add https://github.com/RefractSystems/virtmcu --skill spec-driven-development-refractsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting a clear SPEC before coding to prevent misaligned expectations and scope creep across teams.

Core Features & Use Cases

Structured SPEC template covering Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries.
Phase-driven workflow (Specify, Plan, Tasks, Implement) to guide development from idea to ready-to-implement plan.
Open questions and risk management prompts to surface assumptions early.

Quick Start

Draft a clear SPEC for the new feature before writing any code.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I write a software specification to prevent scope creep?▼

Drafting a clear SPEC before coding prevents misaligned expectations and scope creep by capturing requirements in a fixed six-element structure: Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries.

What should be included in a project specification for new architectural decisions?▼

A project specification should include Objective, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries, while also capturing open questions, risks, and success criteria to surface assumptions during architectural decisions.

When do I need to define a SPEC before coding?▼

Define a SPEC before coding during early project phases for new projects or architectural decisions, specifically when requirements are unclear or multi-file changes are likely, to prevent scope creep across teams.

How do I guide development from an idea to a ready-to-implement plan?▼

Use a phase-driven workflow of Specify, Plan, Tasks, and Implement to guide development from idea to a ready-to-implement plan, ensuring requirements are defined and assumptions are surfaced before coding.

Does defining requirements before coding work for multi-file changes?▼

Yes, defining requirements before coding works for multi-file changes by applying a structured SPEC early in the project phase, which aligns expectations and reduces ambiguity when complex modifications are likely.