Spec Driven Development
Steer agents through spec-first planning and implementation instead of unstructured vibe coding.
Overview
io.github.formulahendry/spec-driven-development is a Validate-phase MCP server that facilitates spec-driven agent workflows instead of unstructured vibe coding.
What is this MCP server?
- MCP server oriented to spec-driven development rather than ad hoc generation
- npm package mcp-server-spec-driven-development at version 0.1.1
- Stdio MCP transport for Claude Code, Cursor, and similar clients
- GitHub source at formulahendry/mcp-server-spec-driven-development
- Bridges product intent and agent execution with explicit workflow facilitation
- Published server version 0.1.1
- npm identifier mcp-server-spec-driven-development with stdio transport
- GitHub repository formulahendry/mcp-server-spec-driven-development
What problem does it solve?
Prompt-only development lets agents ship plausible code that misses requirements you never wrote down.
Who is it for?
Indie builders who want lightweight spec discipline while still coding primarily through agents.
Skip if: Teams that only need a one-shot code generator with no requirements artifact or governance habit.
What do I get? / Deliverables
After you add the server, agents can follow spec-driven MCP workflows so features align with explicit scope before and during implementation.
- MCP-mediated spec-driven development sessions with your agent
- Clearer traceability from scope documents to implementation steps
- Reduced drift compared to unstructured prompt-only coding
Recommended MCP Servers
Journey fit
Specs and bounded scope belong in Validate before you commit to a full Build, even though the workflow continues into implementation. Scope is the canonical shelf because the server promotes written requirements and acceptance criteria before code volume grows.
How it compares
Process-oriented MCP workflow server, not a language runtime or generic registry browser.
Common Questions / FAQ
Who is spec-driven-development for?
Solo builders and small teams using MCP agents who want specifications to lead coding sessions rather than retrofitted documentation.
When should I use spec-driven-development?
Use it when scoping an MVP, drafting feature specs, or enforcing that agent changes trace back to written requirements before merge.
How do I add spec-driven-development to my agent?
Install mcp-server-spec-driven-development from npm, register it as a stdio MCP server in your agent config, restart, then invoke its workflow tools at the start of a feature.