spec-driven-development

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger

When starting a new project, feature, or significant change
When requirements are unclear, ambiguous, or only exist as a vague idea

Mechanism

Four-phase gated workflow: spec → plan → tasks → implement, each requiring human approval
Surface assumptions first to prevent silent filling of ambiguous requirements
Six core spec areas: objective, commands, project structure, code style, testing strategy, boundaries (always do/ask first/never do)
Don't advance to next phase until current phase is validated

Outcome

Approved specification document serving as the shared source of truth for subsequent planning and implementation

Use Cases

Two Typical Use Cases

Scenario 01

New Project Startup Spec Writing

When starting a new project, the agent writes a complete PRD, clarifying requirements, listing assumptions, and writing six core chapters. The spec requires human approval before proceeding to planning and implementation, preventing wasted effort on wrong understanding.

Scenario 02

Feature Change Spec Update

When existing features need significant changes, the agent updates the spec first, assessing the change impact scope, identifying potentially affected modules and interfaces, and getting stakeholder confirmation before code changes.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

No explicit dependency

Tier 2 · Current Skill

spec-driven-developmentWorkflow

Tier 3 · I Use These Skills

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md100.0%

▸skills/spec-driven-development/
▸spec-driven-development
- ·SKILL.md

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

api-and-interface-design

Guides agents to design stable, hard-to-misuse public interfaces using contract-first principles. Covers REST, GraphQL, module boundaries, component props, emphasizing Hyrum's Law, One-Version Rule, error semantics, and boundary validation. Produces consistent, maintainable, well-documented interface specifications.

Workflow

browser-testing-with-devtools

Browser testing skill that gives agents live browser runtime visibility via Chrome DevTools MCP. Supports DOM inspection, console log capture, network request analysis, performance profiling, and visual output verification. Bridges the gap between static code analysis and live browser execution.

CLI Manual

ci-cd-and-automation

CI/CD automation skill that guides agents to set up and maintain automated build and deployment pipelines. Emphasizes shifting quality gates left, integrating tests, lint, type checking, and build verification into every change. Follows the "smaller is faster is safer" principle with frequent small releases.

Workflow

code-review-and-quality

Code review and quality skill that guides agents to conduct multi-axis code reviews covering correctness, design, maintainability, security, and performance. Emphasizes change sizing (~100 lines), severity labels (Nit/Optional/FYI), and splitting strategies to ensure code quality before every merge.

Workflow

When It Triggers · How It Works · What It Produces

Trigger

Mechanism

Outcome

Two Typical Use Cases

New Project Startup Spec Writing

Feature Change Spec Update

Which Skills I Use · Which Skills Use Me

Full Relationship Graph

SKILL.md

Skill Composition

You May Also Need These Skills

api-and-interface-design

browser-testing-with-devtools

ci-cd-and-automation

code-review-and-quality

/spec-driven-development

Two Typical Use Cases

New Project Startup Spec Writing

Feature Change Spec Update

SKILL.md

Skill Composition

When It Triggers · How It Works · What It Produces

Trigger

Mechanism

Outcome

You May Also Need These Skills

api-and-interface-design

browser-testing-with-devtools

ci-cd-and-automation

code-review-and-quality

Which Skills I Use · Which Skills Use Me

Full Relationship Graph