Ad space · Your tool here
PluginStack
Rules & Prompts · by GitHub

Spec Kit

Spec Kit official site ↗

Last checked against the official docs:

What it does

GitHub's open-source toolkit for spec-driven development: you write down what to build and why, then have your coding agent turn that spec into a plan, a task list and working code, one reviewed step at a time. The Specify CLI (specify) sets up a project with the commands for your agent, and extensions add other workflows such as bug fixing (assess, fix, test). It works with GitHub Copilot, Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Cline, Kilo Code, Goose and others. MIT licensed.

Who it's for

Anyone who wants an AI agent to build a feature from a written spec and plan instead of one long prompt, and to review each stage before code gets written.

How to set it up

  1. You need Python 3.11+, uv and a supported AI coding agent (Linux, macOS or Windows). Install the CLI and create a project. Swap copilot for your agent's integration key, such as claude, cursor-agent, codex, gemini or opencode:

    bash
    uv tool install specify-cli
    specify init my-project --integration copilot
    cd my-project
  2. Start your coding agent in the project folder and run these in the agent's chat (not your terminal), one at a time, reviewing each result before the next. Create the constitution once per project and repeat the rest for each feature:

    text
    /speckit-constitution Create principles focused on code quality, testing, and maintainability.
    /speckit-specify Build a photo organizer with albums grouped by date.
    /speckit-plan Use Vite with vanilla JavaScript. Store metadata in SQLite.
    /speckit-tasks
    /speckit-implement
    /speckit-converge
  3. The command prefix depends on the agent (Codex, for example, uses $speckit-specify). Repeat implement and converge until converge reports Converged. To fix a bug without the full feature flow, add the bug extension from the project folder:

    bash
    specify extension add bug
  4. Already installed an old version? uv tool install keeps the installed copy, so upgrade with uv tool install --force specify-cli. Very old CLIs fail with "No such option: --integration". Check what you have with specify version. Community extensions and presets in Spec Kit's catalogs aren't audited, so read their code before installing.

Check the official Spec Kit docs for the latest steps.

Set it up / Fixes

Step-by-step guides for getting Spec Kit running and fixing common errors.

Example prompts

prompt
/speckit-specify Add a CSV export to the reports page so users can download the filtered table.
prompt
/speckit-plan Keep the existing Next.js App Router setup and don't add new dependencies.
prompt
/speckit-bug-assess "Submitting an empty password crashes the login form." slug=login-crash

Made Spec Kit? Add the badge

If you like, show that Spec Kit is listed and hand-checked here. It's optional: listings are free and we never ask for a link back.

Hand-checked on PluginStack
Get the Markdown or HTML

Markdown (for a GitHub README)

markdown
[![Hand-checked on PluginStack](https://www.pluginstackai.com/badge/hand-checked.svg)](https://www.pluginstackai.com/plugins/spec-kit/)

HTML (for a website)

html
<a href="https://www.pluginstackai.com/plugins/spec-kit/"><img src="https://www.pluginstackai.com/badge/hand-checked.svg" alt="Hand-checked on PluginStack" width="226" height="28"></a>

About the badge

Free: MCP Starter Checklist

After you set this tool up, use the one-page checklist so your next MCP server doesn't fail on first connect.

Markdown download + occasional PluginStack updates. No spam. Privacy policy.

See all Rules & Prompts on PluginStack