Spec-Driven Steroids

Inject Spec-Driven Development into AI coding tools without building a new UI.

What it is

spec-driven-steroids is a CLI plus MCP server plus template bundle for running a strict workflow inside AI coding tools:

requirements -> design -> tasks -> implementation

It injects:

• platform-specific agents, commands, or workflows
• universal writing/implementation skills
• MCP validation tools for spec structure and traceability

Supported platforms

• GitHub Copilot for VS Code
• GitHub Copilot for JetBrains
• OpenCode
• Google Antigravity
• OpenAI Codex
• Claude Code

What gets generated

Spec-Driven planning writes artifacts to:

specs/changes/<slug>/
  requirements.md
  design.md
  tasks.md

The workflow is built around:

• EARS requirements
• Mermaid design diagrams
• atomic implementation tasks
• requirement/design/task traceability

Installation

npm install -g spec-driven-steroids

Requirements:

• Node.js >=20
• pnpm for local development

Quick start

1. Inject platform files into a repository:

spec-driven-steroids inject

2. Generate project guidance first:

• use /inject-guidelines in supported tools
• this creates AGENTS.md, CONTRIBUTING.md, STYLEGUIDE.md, TESTING.md, ARCHITECTURE.md, and SECURITY.md

3. Start the spec flow:

• GitHub Copilot: @spec-driven Add a rate limiter to the API
• OpenCode: use the Spec-Driven agent
• Antigravity: /spec-driven
• Codex: /spec-driven Add a rate limiter to the API

4. Approve each planning phase as it completes, then move to implementation.

Validation tools

The bundled MCP server provides 5 tools:

Tool	Purpose
verify_spec_structure	Validate spec folder structure
verify_requirements_file	Validate EARS requirements
verify_design_file	Validate design structure and Mermaid usage
verify_tasks_file	Validate task structure and traceability
verify_complete_spec	Validate the full spec end to end

Optional: Sequential-Thinking MCP

For agents working on complex, long-running tasks, you can optionally add the sequential-thinking MCP server alongside the internal MCP. This provides structured reasoning capabilities to help agents break down complex problems and avoid timeout errors.

During Injection

When running spec-driven-steroids inject, you'll be prompted:

Add sequential-thinking MCP server? (Enables structured reasoning for long-running tasks)

Select Yes to automatically configure both MCP servers.

Manual Configuration

If you need to add it later, add this to your platform's MCP configuration:

VS Code (.vscode/mcp.json):

{
  "servers": {
    "spec-driven-steroids": {
      "command": "node",
      "args": ["path/to/spec-driven-steroids/dist/mcp/index.js"]
    },
    "sequential-thinking": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
    }
  }
}

OpenCode (opencode.json):

{
  "mcp": {
    "spec-driven-steroids": {
      "type": "local",
      "command": ["node", "path/to/spec-driven-steroids/dist/mcp/index.js"]
    },
    "sequential-thinking": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-sequential-thinking"]
    }
  }
}

Requirements

The sequential-thinking MCP is optional and does not affect the internal MCP functionality. To use it:

1. Ensure npx is available in your environment
2. The package @modelcontextprotocol/server-sequential-thinking will be downloaded automatically on first use

For more details, see the long-running-work-planning skill documentation.

Package layout

packages/
  cli/
    src/cli/        CLI injection and validation commands
    src/mcp/        MCP validation server
    templates/      Platform wrappers and universal skills
  test-utils/       Shared fixtures and helpers
  landing-page/     Documentation site

Development

pnpm install
pnpm build
pnpm test

Useful commands:

• pnpm typecheck
• pnpm test:coverage
• pnpm changeset
• pnpm changeset:version

Release flow

This repo publishes the spec-driven-steroids npm package with Changesets and GitHub Actions trusted publishing.

Typical release steps:

pnpm changeset
pnpm changeset:version
pnpm test
pnpm build
git push origin main
git tag -a v<version> -m "release v<version>"
git push origin v<version>

The publish workflow runs from .github/workflows/publish.yml and uses npm trusted publishing through GitHub Actions OIDC, so no long-lived npm token is required in the repository.

Repository docs

• AGENTS.md
• CONTRIBUTING.md
• STYLEGUIDE.md
• TESTING.md
• ARCHITECTURE.md
• SECURITY.md

License

MIT