How do I install the Spec Driven Development skill?

Run npx skillmds@latest add ankurjain1121/spec-driven-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Driven Development safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Driven Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Driven Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Driven Development?

Ankurjain1121 (@ankurjain1121) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Driven Development by ankurjain1121

Name: Spec Driven Development
Author: Ankurjain1121

File contents

Spec-Driven Development Integration

After Phase 3 (Planning) produces API contracts and a coding sequence, this skill generates a specs/ directory compatible with /orchestrate and /implement workflows.

When to Use

Invoke after Phase 3 approval when the user wants to:

Hand off implementation to /orchestrate for parallel execution
Generate a structured spec for /implement to follow
Create a standalone design document for external teams

Output Structure

Generate specs/[project-name]/ with:

specs/[project-name]/
├── design.md              # Architecture overview + key decisions
├── api-contracts.md       # Copy of 03-api-planning/api-contracts.md
├── modules.md             # Module list with file ownership
├── implementation-order.md # From coding-sequence.md
└── constraints.md         # Non-standard paths, API quirks, env vars

design.md Template

# [Project Name] - Design Specification

## Overview
[One paragraph from Phase 1 vision statement]

## Architecture
[Pattern chosen in Phase 2 with rationale]

## Modules

| Module | Purpose | Owner | Files |
|--------|---------|-------|-------|
| [name] | [purpose] | [agent/unassigned] | [file paths] |

## Key Decisions
| ID | Decision | Rationale | Source |
|----|----------|-----------|--------|
| D001 | [decision] | [why] | [URL] |

## Constraints
- [Non-standard paths]
- [API quirks]
- [Required environment variables]

modules.md Template

# Module Ownership

> ONE FILE = ONE OWNER. No shared ownership.

| File Path | Module | Owner | Status |
|-----------|--------|-------|--------|
| src/auth/middleware.ts | Auth | unassigned | pending |
| src/users/controller.ts | Users | unassigned | pending |

Generation Steps

Read 01-discovery/outline-v1.md for vision
Read 01-discovery/decisions-log.md for key decisions
Read 02-structure/module-hierarchy.md for module list
Read 03-api-planning/api-contracts.md for API specs
Read 03-api-planning/coding-sequence.md for implementation order
Read 00-project-state.json for critical details
Generate all spec files

Compatibility

The generated specs are compatible with:

/orchestrate - reads modules.md for file ownership, implementation-order.md for sequencing
/implement - reads design.md for architecture context, api-contracts.md for endpoints
External teams - standalone documentation that doesn't require framework-dev plugin

---name: spec-driven-developmentdescription: Use when generating specs/ compatible output after Phase 3, enabling handoff to /orchestrate or /implement workflows.---# Spec-Driven Development IntegrationAfter Phase 3 (Planning) produces API contracts and a coding sequence, this skill generates a `specs/` directory compatible with `/orchestrate` and `/implement` workflows.---## When to UseInvoke after Phase 3 approval when the user wants to:- Hand off implementation to `/orchestrate` for parallel execution- Generate a structured spec for `/implement` to follow- Create a standalone design document for external teams---## Output StructureGenerate `specs/[project-name]/` with:```specs/[project-name]/├── design.md # Architecture overview + key decisions├── api-contracts.md # Copy of 03-api-planning/api-contracts.md├── modules.md # Module list with file ownership├── implementation-order.md # From coding-sequence.md└── constraints.md # Non-standard paths, API quirks, env vars```---## design.md Template```markdown# [Project Name] - Design Specification## Overview[One paragraph from Phase 1 vision statement]## Architecture[Pattern chosen in Phase 2 with rationale]## Modules| Module | Purpose | Owner | Files ||--------|---------|-------|-------|| [name] | [purpose] | [agent/unassigned] | [file paths] |## Key Decisions| ID | Decision | Rationale | Source ||----|----------|-----------|--------|| D001 | [decision] | [why] | [URL] |## Constraints- [Non-standard paths]- [API quirks]- [Required environment variables]```---## modules.md Template```markdown# Module Ownership> ONE FILE = ONE OWNER. No shared ownership.| File Path | Module | Owner | Status ||-----------|--------|-------|--------|| src/auth/middleware.ts | Auth | unassigned | pending || src/users/controller.ts | Users | unassigned | pending |```---## Generation Steps1. Read `01-discovery/outline-v1.md` for vision2. Read `01-discovery/decisions-log.md` for key decisions3. Read `02-structure/module-hierarchy.md` for module list4. Read `03-api-planning/api-contracts.md` for API specs5. Read `03-api-planning/coding-sequence.md` for implementation order6. Read `00-project-state.json` for critical details7. Generate all spec files---## CompatibilityThe generated specs are compatible with:- `/orchestrate` - reads `modules.md` for file ownership, `implementation-order.md` for sequencing- `/implement` - reads `design.md` for architecture context, `api-contracts.md` for endpoints- External teams - standalone documentation that doesn't require framework-dev plugin

Frequently asked questions

Spec Driven Development