spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: front-depiction

Guide six-phase spec-driven development workflows with explicit approvals between phases.

Updated Aug 27, 2026

Search Tags:#design #planning #spec-driven #requirements #implementation #phase-based #behavioral-tests

Ready to run

npx skills add https://github.com/front-depiction/claude-setup --skill spec-driven-development-front-depiction

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/front-depiction/claude-setup/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/front-depiction/claude-setup --skill spec-driven-development-front-depiction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development helps product teams and engineers avoid scope drift by capturing raw requirements, designing solutions, and validating behavior before coding.

Core Features & Use Cases

Six-phase workflow: Instructions, Requirements, Design, Behaviors (executable tests), Plan, and Implementation, enabling living documentation and disciplined delivery.
Phase-by-phase approvals: After each phase, explicit user authorization is required before proceeding.
Living documentation and executable specs: Behavioral tests attached to features drive implementation and serve as ongoing reference.

Quick Start

Create specs/[feature-name]/instructions.md with raw requirements, then progress Phases 2-6 following the six-phase framework, prompting for user approvals after each phase. Provide a sample feature near the top to illustrate, and always return to the user for sign-off between phases.

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 how does it prevent scope drift?▼

Spec-driven development prevents scope drift by capturing raw requirements, designing solutions, and validating behavior before coding. It uses a six-phase workflow with explicit approvals between each phase to ensure product teams and engineers align on features.

How do I document requirements before coding a new feature?▼

To document requirements before coding, create specs/[feature-name]/instructions.md with raw requirements. Then progress through the six phases—Requirements, Design, Behaviors, Plan, and Implementation—prompting for user sign-off after each phase to ensure alignment.

When should I use a phase-based workflow for software engineering tasks?▼

A phase-based workflow should be used for new features, major refactors, API design, and complex bugs. It guides the process by producing living specifications and executable behavioral tests that drive implementation and serve as ongoing reference.

Does spec-driven development support executable behavioral tests?▼

Yes, spec-driven development produces executable behavioral tests attached to features. These tests satisfy testing requirements by driving implementation and serving as living documentation throughout the software engineering lifecycle.

Can I use structured planning for major refactors and API design?▼

Yes, structured planning applies to major refactors and API design. The six-phase spec-driven workflow captures functional, non-functional, and data requirements, ensuring disciplined delivery and living documentation for complex engineering tasks.

What are the limitations of a six-phase spec-driven workflow?▼

The six-phase spec-driven workflow requires explicit user authorization after each phase, which may slow down rapid prototyping. It is designed for complex features and refactors where avoiding scope drift outweighs the overhead of phase-by-phase approvals.