spec-driven-development

Create a structured specification before coding with a four-phase gated workflow.

Updated Aug 27, 2026

Search Tags:#planning #architecture #documentation #specification #requirements #development-process

Ready to run

npx skills add https://github.com/s0341969/scheduler-project --skill spec-driven-development-s0341969

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/s0341969/scheduler-project/tree/main/.codex/skills/agent-skills/skills/spec-driven-development
Command: npx skills add https://github.com/s0341969/scheduler-project --skill spec-driven-development-s0341969

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development ensures a shared source of truth before coding, reducing miscommunication and rework.

Core Features & Use Cases

Establishes a structured spec covering objectives, commands, project structure, code style, testing strategy, and boundaries.
Supports a gated workflow (SPECIFY → PLAN → TASKS → IMPLEMENT) to reduce ambiguity and errors in large or uncertain projects.
Helps teams align stakeholders at project initiation or when requirements are unclear to align stakeholders and set measurable success criteria.

Quick Start

Draft a concise spec that defines the objective, five core areas (commands, structure, style, testing, boundaries) and the validation process before any code is written.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is spec-driven development and when should I use it?▼

Spec-driven development creates a formal specification before coding to align expectations. Use it at project initiation, feature design, or architectural decisions where requirements are uncertain or detailed guidance is lacking.

How do I create a formal specification before coding?▼

Draft a concise specification covering six core areas: objectives, commands, project structure, code style, testing strategy, and boundaries. Define the validation process before any code is written.

What is the best way to manage development workflow for uncertain requirements?▼

Use a gated four-phase workflow: SPECIFY, PLAN, TASKS, and IMPLEMENT. This structured approach reduces ambiguity and errors in large or uncertain projects.

Does spec-driven development work for aligning stakeholders on measurable success criteria?▼

Yes, spec-driven development helps teams align stakeholders at project initiation or when requirements are unclear, establishing a shared source of truth and setting measurable success criteria.

Why does my development process have miscommunication and rework issues?▼

Miscommunication and rework often occur because coding starts without a shared source of truth. Creating a formal specification before coding ensures alignment and reduces these errors.