spec-driven-development

Convert project requirements into executable plans and code using the spec-kit workflow.

Updated Dec 29, 2025

Search Tags:#workflow #planning #implementation #guidance #docs #spec-kit #spec-driven-development

Ready to run

npx skills add https://github.com/HundredBillion/promiseKits --skill spec-driven-development-hundredbillion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/HundredBillion/promiseKits/tree/main
Command: npx skills add https://github.com/HundredBillion/promiseKits --skill spec-driven-development-hundredbillion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a structured, repeatable workflow for turning project specifications into executable plans and code using the spec-kit approach.

Core Features & Use Cases

Lifecycle guidance: establish a project constitution, articulate specifications, resolve ambiguities, plan implementation, break down tasks, and execute with a traceable workflow.
Onboarding and governance: helps teams onboard new projects quickly and maintain governance with slash commands, templates, and templates in .specify/.
Step-by-step prompts: includes prompts for each phase (constitution, specify, clarify, plan, tasks, implement) to align teams and reduce rework.

Quick Start

Use the spec-kit prompts to initialize a new project and begin the six-phase workflow.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I convert project requirements into executable implementation plans?▼

To convert project requirements into executable implementation plans, use the spec-kit workflow to progress through structured phases: constitution, specify, clarify, plan, tasks, and implement. This establishes a repeatable, traceable lifecycle from initial specification to final code execution.

What is spec-driven development and how does it structure project governance?▼

Spec-driven development is a structured workflow that turns project specifications into code while maintaining governance. It uses a `.specify/` directory with templates and slash commands to align teams, resolve ambiguities, and enforce a repeatable lifecycle from constitution through implementation.

How do I set up the spec-kit workflow for a new software project?▼

To set up the spec-kit workflow, initialize a `.specify/` directory in your project and configure CLAUDE.md slash commands. This provides the necessary templates and step-by-step prompts to start the six-phase lifecycle, ensuring structured governance and clear implementation guidance.

Does spec-driven development work for onboarding new teams to an existing codebase?▼

Yes, spec-driven development helps onboard teams quickly to existing projects by applying structured governance. The spec-kit workflow uses phase-specific prompts and templates to articulate specifications, resolve ambiguities, and establish a traceable plan, reducing rework and aligning new members.

What is the best way to reduce rework when planning software implementation tasks?▼

The best way to reduce rework during implementation planning is to use a structured spec-kit workflow with phase-specific prompts. By separating the clarify, plan, and tasks phases, teams resolve ambiguities and align on executable steps before writing any code, ensuring consistent outcomes.

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

You should avoid spec-driven development if your project cannot accommodate a `.specify/` directory or the structured six-phase lifecycle. The workflow requires executing prompts for constitution, specify, clarify, plan, tasks, and implement, which may not suit rapid prototyping lacking formal governance.