# mcp-server-spec-driven-development

The mcp-server-spec-driven-development skill guides a project from EARS requirements to a design document and generated code. Use it when you want those steps to build on one another.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 175 installs · ★ 9 repo stars
- Author: reason-machines
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/reason-machines/mcp-skills/tree/HEAD/skills/mcp-server-spec-driven-development/SKILL.md
- Updated: 2026-10-09
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/mcp-server-spec-driven-development

## What it does

The skill lays out a three-stage process: write requirements in EARS format, derive a design document from them, then generate implementation code from the design. Requirements are organized into functional and non-functional groups, and design choices are mapped back to the requirements.

The stages use `generate-requirements`, `generate-design-from-requirements`, and `generate-code-from-design`. The first creates `specs/requirements.md`; the next produces `specs/design.md`; the final stage writes implementation files in the project root. The design stage needs the requirements file, and code generation needs the design document. Without those files, the later steps cannot proceed.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/mcp-skills --skill mcp-server-spec-driven-development -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/mcp-server-spec-driven-development/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/mcp-server-spec-driven-development/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/mcp-skills --skill mcp-server-spec-driven-development -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/mcp-server-spec-driven-development/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/mcp-skills --skill mcp-server-spec-driven-development -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/mcp-server-spec-driven-development/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install reason-machines/mcp-skills skills/mcp-server-spec-driven-development
```

2. **Manually: put the files in place**
- File: `.github/skills/mcp-server-spec-driven-development/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/mcp-skills --skill mcp-server-spec-driven-development -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/reason-machines/mcp-skills --path skills/mcp-server-spec-driven-development
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/mcp-server-spec-driven-development/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add reason-machines/mcp-skills --skill mcp-server-spec-driven-development -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/reason-machines/mcp-skills/tree/HEAD/skills/mcp-server-spec-driven-development/SKILL.md

## When to use it
- write requirements in EARS format
- separate functional and non-functional requirements
- derive a design document from requirements
- generate implementation files from a design
- trace design decisions back to requirements

## Example prompts
- Write my project requirements in EARS format and save them as `specs/requirements.md`.
- Turn `specs/requirements.md` into an architecture and design document at `specs/design.md`.
- Generate implementation files in the project root based on `specs/design.md`.

## Similar
- [spec-driven-development](https://affpapa.org/en/nevibecode/mcp/spec-driven-development.md) — MCP server · ★ 441 repo stars
- [tlc-spec-driven](https://affpapa.org/en/nevibecode/skills/tlc-spec-driven.md) — skill · 1300 installs
- [spec-driven-workflow-v1](https://affpapa.org/en/nevibecode/rules/spec-driven-workflow-v1.md) — rule · ★ 41430 repo stars
- [spec-driven](https://affpapa.org/en/nevibecode/plugins/spec-driven.md) — plugin · ★ 1596 repo stars
- [sdd-spec-writer](https://affpapa.org/en/nevibecode/agents/sdd-spec-writer.md) — subagent · 252 installs
- [spec-kit](https://affpapa.org/en/nevibecode/skills/spec-kit.md) — skill · 167 installs

From the same set: [reason-machines/mcp-skills](https://affpapa.org/en/nevibecode/by/reason-machines/mcp-skills.md) — 98 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
