spec-driven-development

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

Define a formal spec before coding to guide planning and implementation.

Updated Apr 9, 2026

Search Tags:#workflow #planning #documentation #specification #requirements #software-engineering

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill spec-driven-development-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/spec-driven-development
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill spec-driven-development-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured planning and discovery before coding to prevent misalignment and rework by anchoring all decisions in a living spec.

Core Features & Use Cases

Provides a four-phase gated workflow: Specify, Plan, Tasks, Implement, with reviews to ensure alignment.
Documents objective, scope, commands, project structure, code style, testing strategy, boundaries, and success criteria in a single source of truth.
Useful at project inception, feature bets, or major refactors where requirements are unclear or evolving.

Quick Start

Draft a concise spec before coding and share it with the team to ensure alignment.

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 project misalignment?▼

A software specification prevents misalignment by consolidating objective, scope, commands, project structure, code style, testing strategy, boundaries, and success criteria into a single source of truth before coding begins.

When should I use a spec-driven workflow for software development?▼

Use a spec-driven workflow at project inception, for feature bets, or during major refactors when requirements are unclear, ambiguous, or evolving. It anchors decisions in a living spec to reduce rework.

What is the best way to document requirements before coding a new feature?▼

The best way to document requirements is applying a gated four-phase workflow: Specify, Plan, Tasks, and Implement. This ensures reviews align expectations before guiding the plan, tasks, and implementation.

How do I structure a specification document for evolving software requirements?▼

Structure the specification document by defining the objective, commands, project structure, code style, testing strategy, boundaries, and success criteria. This creates an actionable living spec that adapts to evolving requirements.

Does spec-driven development work for major code refactors?▼

Yes, spec-driven development works for major refactors by applying a structured planning and discovery phase beforehand. This anchors implementation decisions in a formal spec to prevent misalignment and reduce rework.