mcp-server-spec-driven-development

Generates requirements, design documents, and code through a three-stage EARS-based workflow.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/mcp-skills --skill mcp-server-spec-driven-development-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-server-spec-driven-development
Source: https://github.com/reason-machines/mcp-skills/tree/main/skills/mcp-server-spec-driven-development
Command: npx skills add https://github.com/reason-machines/mcp-skills --skill mcp-server-spec-driven-development-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp-server-spec-driven-development.

What problem does it solve? Unstructured "vibe coding" leads to unclear requirements, missing features, and implementations that drift from intent. This Skill enforces a systematic requirements → design → code workflow with full traceability between stages. ## Core Features & Use Cases - EARS Requirements Generation: Creates structured requirements documents in specs/requirements.md using the EARS format (Ubiquitous, Event-driven, Unwanted behavior, State-driven, Optional). - Design Document Generation: Reads requirements and produces specs/design.md with architecture, components, data models, and API design. - Code Generation from Design: Generates implementation files (components, composables, configuration) directly from the design document. - Use Case: Describe "a Vue.js todo app with local storage persistence" and receive EARS requirements, a component-level design document, and working TypeScript/Vue code in three guided steps. ## Quick Start Install the MCP server via npx in your mcp.json, then ask your AI assistant to generate requirements using the EARS format for your project idea.

Frequently Asked Questions about mcp-server-spec-driven-development

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

FAQPage Schema
How do I set up spec-driven development with an MCP server?▼

Add the server to your mcp.json with command "npx" and args "-y mcp-server-spec-driven-development@latest", then restart your IDE. Three prompts become available: generate-requirements, generate-design-from-requirements, and generate-code-from-design.

What is the EARS format for software requirements?▼

EARS (Easy Approach to Requirements Syntax) structures requirements into five types: Ubiquitous (SHALL), Event-driven (WHEN), Unwanted behavior (IF), State-driven (WHILE), and Optional (MAY). It ensures requirements are clear, testable, and unambiguous.

How do I generate code from a design document?▼

Run the generate-code-from-design prompt after specs/design.md exists. The server reads the design file and generates implementation files including components, composables, and configuration in your project root.

Why does generate-design-from-requirements fail with file not found?▼

The prompt requires specs/requirements.md to exist in your project root. Run generate-requirements first, and verify the file is located at specs/requirements.md relative to the project root.

Can I use spec-driven development for large multi-module projects?▼

Yes, create separate requirement and design documents per module, such as requirements-auth.md and design-api.md under specs/. Then run the generation prompts for each module separately.