Spec Driven Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Spec Driven Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A Model Context Protocol (MCP) server that provides structured project specification management capabilities for AI editors through a specification-driven development workflow.
Build a TODO Web app like Microsoft Todo, using Spec-driven development mode
Build a TODO Web app like Microsoft Todo, using Spec-driven development mode, just want the requirements and tasks stage, and then complete the workflow.
Initialize the specification-driven project structure and templates.
Purpose: Create the foundational directory structure and template files required for specification-driven development.
Features:
.spec/ and .spec/template/ directoriesParameters: No parameters required
Start a specification-driven development workflow.
Parameters:
requirements_prompt (string, optional): User requirement description. Required for requirements stage. Used to convert user requirements into structured specifications.stage (enum, optional): Jump directly to specified stage ("requirements", "design", "tasks"). If not specified, automatically detects current stage.next_stage (enum, optional): Specify next stage after completion ("design", "tasks", null). Allows LLM to intelligently choose workflow path based on requirement complexity.Workflow Stages:
Usage Patterns:
requirements → design → tasksrequirements → tasks (skip design)requirements → complete| Role | Core Position | Primary Responsibilities |
|---|---|---|
| 🤖 LLM | Intelligent Analyzer & Decision Maker | • Analyze requirement complexity and infer next_stage values<br>• Generate all .spec/*.md file content<br>• Make technical routing decisions based on complexity assessment<br>• Process user requirements into structured requirements_prompt |
| 👤 User | Requirement Owner & Quality Controller | • Clearly express desired features and functionality<br>• Review generated documentation to ensure it meets actual requirements<br>• Control workflow progress (continue/restart/modify)<br>• Provide project context that influences implementation decisions |
| 🔧 Tool | Workflow Orchestrator | • Automatically detect current stage and manage requirements → design → tasks progression<br>• Validate workflow dependencies before stage transitions<br>• Provide structured prompts for LLM content creation<br>• Provide clear guidance when dependencies are missing or parameters are invalid |
It is not recommended to install this as a global MCP tool. Please install it in your workspace.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"spec-driven": {
"command": "npx",
"args": ["-y", "spec-driven-mcp"],
"env": {
"SPEC_ROOT_DIR": "/path/to/workspace"
}
}
}
}Add the following to your .cursor/mcp.json or VS Code MCP settings:
{
"mcpServers": {
"spec-driven": {
"command": "npx",
"args": ["-y", "spec-driven-mcp"],
"env": {
"SPEC_ROOT_DIR": "/path/to/workspace"
}
}
}
}Edit template files in the .spec/template/ directory to customize the generated specification format. Each call to create_spec uses the latest template version to generate specification prompts.
Template Files:
requirements.md: User story format with acceptance criteriadesign.md: Architecture design including component relationshipstasks.md: Implementation checklist with specific actionable taskspnpm watch # Development mode with auto-reload
pnpm build # Production buildMIT License
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.