sdd-mcp

Provides spec-driven development tools and MCP workflows for spec management, steering, validation, and implementation.

typescript

13

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "yuki-yano-sdd-mcp": {
      "command": "bunx",
      "args": [
        "sdd-mcp@latest"
      ]
    }
  }
}

You are using a spec-driven MCP server that provides dedicated slash commands to assist you in managing specs, validating designs, and guiding implementation. This server streamlines the end-to-end workflow from initial spec through to implementation, with built-in prompts, templates, and quality checks that keep your development aligned with your goals.

How to use

You work with MCP clients to invoke specialized tools for specification management, steering documents, and validation. Each tool loads its template, fills in parameters, and returns metadata such as template_id and version. Use the tools to initialize specs, define requirements, design, break tasks, implement with TDD, check status, and capture feedback. Review outputs in your project’s steering and specs folders to keep humans in control of the process.

How to install

bunx sdd-mcp@latest

npx sdd-mcp@latest

Configuration and usage notes

Prerequisites include a runtime and environment capable of running the MCP server. The recommended setup uses Bun, with Node.js 20+ also supported. You can start the server using either of the provided invocation methods, depending on your preferred runtime.

Usage patterns and tips

Start the server using a preferred runner: bunx sdd-mcp@latest or npx sdd-mcp@latest. - Invoke tools from an MCP client by referencing the available commands under the MCP tool namespace. - Use the steering documents to maintain project-wide context when context feels stale. - Validate designs and gaps before shipping to ensure alignment with requirements.

Notes on workflow

Follow the spec-driven workflow: initialize a spec, generate requirements, create a design, break down tasks, implement with TDD, and then check status. Capture feedback and apply changes to ensure ongoing alignment across requirements, design, and tasks.

Available tools

spec-init

Initialize a new specification from the project description to establish a baseline.

spec-requirements

Generate a comprehensive requirements definition based on the initialized spec.

spec-design

Generate a design document aligned with approved requirements to guide implementation.

spec-tasks

Break down the design into concrete implementation tasks for tracking.

spec-impl

Execute implementation using a Test-Driven Development approach.

spec-status

Check current status of the specification, including phases and progress.

spec-feedback

Capture and apply feedback, producing JSON/Markdown reports and updating spec docs.

steering

Update project-wide steering documents controlling direction and priorities.

steering-custom

Create custom steering documents for additional context.

validate-design

Review design quality and provide recommendations.

validate-gap

Analyze gaps between requirements and implementation.