spec-driven-development

Create formal spec documents with a six-section template before coding.

9|Updated Dec 20, 2025

Search Tags:#planning #specification #requirements #engineering #project-management #phase-based-workflow

Ready to run

npx skills add https://github.com/christopher-buss/flux --skill spec-driven-development-christopher-buss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/christopher-buss/flux/tree/main/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/christopher-buss/flux --skill spec-driven-development-christopher-buss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development locks in requirements before coding by providing a formal, shared spec document that aligns engineers and stakeholders.

Core Features & Use Cases

Structured six-phase workflow (Specify → Plan → Tasks → Implement) that guides teams from idea to deliverable.
Spec templates and success criteria to ensure testability, traceability, and scope control.
Open-questions and boundary management to surface assumptions, resolve conflicts, and prevent scope creep.

Quick Start

Draft a concrete spec document covering objective, commands, project structure, code style, testing strategy, and boundaries before starting any coding task.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I turn vague project ideas into precise testable specifications?▼

To turn vague ideas into testable specifications, use a structured workflow that locks in requirements before coding by producing a formal spec document covering objectives, project structure, code style, testing strategy, and boundaries to align stakeholders.

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

Spec-driven development is a formal process that locks in requirements before coding by creating a shared spec document. Apply it to new projects, architectural changes, or features with evolving or unclear requirements to create a concrete plan before implementation.

How do I prevent scope creep when planning features with unclear requirements?▼

Prevent scope creep during feature planning by using a specification document with explicit success criteria and boundary management. This surfaces assumptions, resolves conflicts via open-questions, and enforces a phased workflow to guide teams from idea to deliverable.

What's the best way to structure a project specification before starting implementation?▼

The best way to structure a project specification is using a six-section template covering objective, commands, project structure, code style, testing strategy, and boundaries, processed through a phased Specify, Plan, Tasks, and Implement workflow.

Does spec-driven development work for architectural changes in existing projects?▼

Yes, spec-driven development works for architectural changes in existing projects by applying a formal spec template and phased workflow. It creates a concrete plan with explicit success criteria to align engineers and stakeholders before implementation begins.

When should I not use a formal specification workflow for software engineering?▼

You should avoid using a formal specification workflow for simple, well-defined tasks where requirements are already clear, as the six-phase Specify to Implement process and strict template enforcement add planning overhead best suited for complex or evolving features.