skills.rest
Aradotso
AradotsoOFFICIAL
Explore all skills by this author →
Website𝕏@aradotsoGitHub

mcp-server-spec-driven-development

Generate EARS requirements, design documents, and code in a three-stage workflow.

7|2|Updated May 16, 2026
Search Tags:#software design#code generation#traceability#requirements engineering#spec-driven development#ears format
One-click install
npx skills add https://github.com/Aradotso/mcp-skills --skill mcp-server-spec-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-server-spec-driven-development
Source: https://github.com/Aradotso/mcp-skills/tree/main/skills/mcp-server-spec-driven-development
Command: npx skills add https://github.com/Aradotso/mcp-skills --skill mcp-server-spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates vague, hard-to-track software development by forcing a disciplined flow from requirements to design to implementation, preserving traceability and reducing rework.

Core Features & Use Cases

  • Spec-first execution with EARS format: Generates structured, testable requirements using Ubiquitous, Event-driven, Unwanted behavior, State-driven, and Optional statements.
  • Requirements-to-design mapping: Produces an architecture and component design document that links decisions back to requirements.
  • Design-to-code generation: Implements the described components, utilities, and configuration files from the design document to reduce manual implementation drift.
  • Use case: When building a medium-size web app feature, you can generate EARS requirements, transform them into an architecture/design, and then generate the corresponding implementation consistently across iterations.

Quick Start

Ask for requirements in EARS format for your app, then run the design generation prompt, and finally run the code generation prompt to produce implementation files.

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 generate code from software requirements automatically?▼

Spec-driven development generates code from requirements by first creating an EARS format requirements.md, deriving a design.md, and then implementing the code to maintain requirements-to-code traceability.

What is EARS format in requirements engineering?▼

EARS format structures software requirements into Ubiquitous, Event-driven, Unwanted behavior, State-driven, and Optional statements to eliminate ambiguity and create testable specifications.

How do I keep my software design aligned with written specifications?▼

You can keep design aligned with specifications by using a spec-driven workflow that maps requirements directly to architecture decisions and then generates implementation files from that design document.

Can I use spec-driven development for full-stack web application features?▼

Yes, spec-driven development applies to web, backend, and full-stack projects, allowing you to generate EARS requirements, transform them into architecture designs, and produce corresponding implementation code.

What is the best way to trace software features back to their original requirements?▼

Traceability is achieved by enforcing a three-stage dependency flow that generates design documents directly from requirements and subsequently generates code files mapped to those design decisions.

Why does my generated code drift from the initial software design?▼

Implementation drift happens when code is written manually without design traceability; generating code directly from a design.md file derived from EARS requirements reduces this drift.

Related Skills

Explore More Software Engineering Skills→
suriyelsuriyel
178

long-task-requirements

Generates an SRS document from structured software requirements elicitation.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

constitution-enforcer

Validate project governance against 9 Constitutional Articles and Phase -1 Gates.

Community
Advanced
m19803261706m19803261706

cx-fix

Investigate, fix, test, and commit code changes with conventional commits.

Community
Intermediate
chidekinachidekina
2

prompt-modeler

Generate structured planning and design prompts from project briefs.

Community
Advanced