Skip to content
Back to search

spec-kit

💫 Toolkit to help you get started with SDD or any other process!

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/github/spec-kit with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/github/spec-kit'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/github--spec-kit/badge.svg)](/listings/github--spec-kit)

HTML

<a href="/listings/github--spec-kit"><img src="/api/listings/github--spec-kit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 268 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src="https://raw.githubusercontent.com/github/spec-kit/main/media/logo_large.webp" alt="Spec Kit Logo" width="200" height="200"/>
  3. <h1>🌱 Spec Kit</h1>
  4. <h3><em>Build with a spec, fix a bug, or assess an idea — with your coding agent.</em></h3>
  5. </div>
  6. <p align="center">
  7. <a href="https://github.com/github/spec-kit/releases/latest"><img src="https://img.shields.io/github/v/release/github/spec-kit" alt="Latest Release"/></a>
  8. <a href="https://github.com/github/spec-kit/stargazers"><img src="https://img.shields.io/github/stars/github/spec-kit?style=social" alt="GitHub stars"/></a>
  9. <a href="https://github.com/github/spec-kit/blob/main/LICENSE"><img src="https://img.shields.io/github/license/github/spec-kit" alt="License"/></a>
  10. <a href="https://github.github.io/spec-kit/"><img src="https://img.shields.io/badge/docs-GitHub_Pages-blue" alt="Documentation"/></a>
  11. </p>
  12. <p align="center">
  13. <strong>English</strong> ·
  14. <a href="./README.zh-CN.md">简体中文</a> ·
  15. <a href="./README.ja.md">日本語</a> ·
  16. <a href="./README.ko.md">한국어</a>
  17. </p>
  18. Spec Kit is an open source toolkit that gives AI coding agents structured
  19. processes, reusable templates, and documented outcomes. Start with a ready-made
  20. process, customize it, or bring your own.
  21. ## Choose your process
  22. | What you need | Process | Outcome |
  23. | --- | --- | --- |
  24. | Build a feature or application | [Spec-Driven Development](#spec-driven-development) | A specification carried through planning, implementation, and convergence |
  25. | Diagnose and repair broken behavior | [Bug fixing](#bug-fixing) | An assessed cause, scoped fix, and recorded verification |
  26. | Decide whether an idea deserves investment | [Idea assessment](#idea-assessment) | An evidence-backed go, clarify, or stop decision |
  27. | Adopt or create a different process | [Your own process](#capabilities) | A process adapted or assembled from reusable primitives |
  28. These are independent entry points, not mandatory phases. SDD ships in core;
  29. bug fixing and assessment are bundled extensions you install when needed, and
  30. the primitives below let you adopt or create other processes.
  31. ## Capabilities
  32. Spec Kit combines ready-to-use processes with composable mechanisms:
  33. | Capability | Spec Kit mechanism |
  34. | --- | --- |
  35. | Connect to or switch between coding agents | [Integration](https://github.github.io/spec-kit/integrations/index.html) |
  36. | Add a command, quality gate, or complete process | [Extension](https://github.github.io/spec-kit/extensions/overview.html) |
  37. | Connect a process to an external tool or service | [Extension](https://github.github.io/spec-kit/extensions/overview.html) |
  38. | React to coding-agent lifecycle events | [Extension runtime event](https://github.github.io/spec-kit/extensions/api.html#extension-runtime-events) |
  39. | Run extension commands before or after Spec Kit commands | [Extension hook](https://github.github.io/spec-kit/extensions/api.html#hook-configuration) |
  40. | Adapt templates, commands, terminology, or methodology | [Preset](https://github.github.io/spec-kit/presets/overview.html) |
  41. | Enforce organizational or regulatory standards | [Preset](https://github.github.io/spec-kit/presets/overview.html) |
  42. | Override a template for one project | [Project-local override](https://github.github.io/spec-kit/how-to/customization.html#project-local-overrides-and-resolution) |
  43. | Automate prompts, commands, gates, and shell tasks | [Workflow](https://github.github.io/spec-kit/workflows/overview.html) |
  44. | Modify an installed workflow without forking it | [Workflow overlay](https://github.github.io/spec-kit/workflows/overlays.html) |
  45. | Add reusable executable behavior to workflows | [Workflow step](https://github.github.io/spec-kit/workflow-steps/developing.html#custom-step-packages) |
  46. | Install a curated setup for a role or team | [Bundle](https://github.github.io/spec-kit/bundles/overview.html) |
  47. | Discover community components | [Catalog](https://github.github.io/spec-kit/overview/catalogs.html) |
  48. | Host a private catalog of approved components | [Catalog](https://github.github.io/spec-kit/overview/catalogs.html) |
  49. | Access private catalogs and component downloads | [Authentication](https://github.github.io/spec-kit/reference/authentication.html) |
  50. | Work offline or behind a firewall | [Local sources and self-hosted catalogs](https://github.github.io/spec-kit/install/air-gapped.html) |
  51. | Inspect which layer supplies a command, template, or script | [Artifact inventory](https://github.github.io/spec-kit/overview/artifacts.html) |
  52. Search the active catalogs with commands such as `specify extension search`,
  53. `specify preset search`, `specify workflow search`, and `specify bundle search`.
  54. Spec Kit includes community catalogs, and organizations can add their own
  55. curated sources. Catalog listings are not audits or endorsements, so review
  56. community source code before installing or running it.
  57. <a id="-get-started"></a>
  58. <a id="-prerequisites"></a>
  59. ## Get started
  60. You need Python 3.11+, [uv](https://github.github.io/spec-kit/install/uv.html),
  61. and a supported AI coding agent on Linux, macOS, or Windows.
  62. Run these commands in your terminal to install Spec Kit and create a project.
  63. This example uses GitHub Copilot.
  64. ```bash
  65. uv tool install specify-cli
  66. specify init my-project --integration copilot
  67. cd my-project
  68. ```
  69. <a id="-supported-ai-coding-agent-integrations"></a>
  70. After installing the Specify CLI and creating your project, launch your coding
  71. agent in the project directory, then choose a process below.
  72. For other setups:
  73. - [Installation](https://github.github.io/spec-kit/installation.html) for pinned releases, other installers, CI, and troubleshooting.
  74. - [Existing projects](https://github.github.io/spec-kit/how-to/existing-projects.html) to start with code you already have.
  75. - [Other agents](https://github.github.io/spec-kit/integrations/index.html) for integration keys and [invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
  76. - [Upgrade](https://github.github.io/spec-kit/upgrade.html) to update an existing installation.
  77. <a id="-what-is-spec-driven-development"></a>
  78. <a id="sdd-quickstart"></a>
  79. ## Spec-Driven Development
  80. Define what to build and why, then turn the specification into a plan, tasks,
  81. and working code.
  82. The minimal flow is shown below. Create a constitution once per project and
  83. repeat the remaining steps for each feature. Run these skills in your agent's
  84. chat, not your terminal, one at a time, reviewing each result before continuing.
  85. This example uses GitHub Copilot's default skills syntax. For another agent,
  86. use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
  87. ```text
  88. /speckit-constitution Create principles focused on code quality, testing, and maintainability.
  89. /speckit-specify Build a photo organizer with albums grouped by date and a tile preview of each album.
  90. /speckit-plan Use Vite with vanilla JavaScript. Keep images local and store metadata in SQLite.
  91. /speckit-tasks
  92. /speckit-implement
  93. /speckit-converge
  94. ```
  95. Repeat implement and converge until convergence reports `Converged`.
  96. For clarification, checklists, and consistency analysis, see the SDD walkthrough.
  97. [SDD walkthrough](https://github.github.io/spec-kit/quickstart.html) ·
  98. [Command reference](https://github.github.io/spec-kit/reference/agentic-sdd.html)
  99. <a id="-bug-fixing-with-spec-kit"></a>
  100. <a id="bug-fix-quickstart"></a>
  101. ## Bug fixing
  102. Assess the cause, fix the bug, and verify the original symptom is resolved.
  103. No SDD feature workflow is required first.
  104. Install the bug-fixing extension in your terminal, from the project directory:
  105. ```bash
  106. specify extension add bug
  107. ```
  108. Run these skills in your agent's chat, not your terminal, one at a time,
  109. reviewing each result before continuing.
  110. This example uses GitHub Copilot's default skills syntax. For another agent,
  111. use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
  112. ```text
  113. /speckit-bug-assess "Submitting an empty password crashes the login form." slug=login-crash
  114. /speckit-bug-fix slug=login-crash
  115. /speckit-bug-test slug=login-crash
  116. ```
  117. Review the reports in `.specify/bugs/login-crash/`. The final verdict is
  118. `verified`, `partial`, or `failed`; only `verified` confirms a successful fix.
  119. [Bug-fixing walkthrough](https://github.github.io/spec-kit/guides/bugfix.html) ·
  120. [Command reference](https://github.github.io/spec-kit/reference/agentic-bugfix.html)
  121. <a id="-assessing-ideas-with-spec-kit"></a>
  122. <a id="idea-assessment-quickstart"></a>
  123. ## Idea assessment
  124. Gather evidence to decide whether an idea is worth pursuing.
  125. No source code or SDD feature workflow is required.
  126. Install the assessment extension in your terminal, from the project directory:
  127. ```bash
  128. specify extension add assess
  129. ```
  130. Run these skills in your agent's chat, not your terminal, one at a time,
  131. reviewing each result before continuing.
  132. This example uses GitHub Copilot's default skills syntax. For another agent,
  133. use its [equivalent invocation syntax](https://github.github.io/spec-kit/integrations/cli.html#command-invocation).
  134. ```text
  135. /speckit-assess-intake "Let users work offline and sync when they reconnect." slug=offline-mode
  136. /speckit-assess-research slug=offline-mode
  137. /speckit-assess-define slug=offline-mode
  138. /speckit-assess-shape slug=offline-mode
  139. /speckit-assess-decide slug=offline-mode
  140. ```
  141. Review the artifacts in `.specify/assessments/offline-mode/` and the final
  142. decision: `go`, `needs-clarification`, or `kill`. Resolve unknowns by editing the
  143. existing Markdown artifacts, directly or with your agent, rather than rerunning
  144. whole stages. If you choose to build a software idea with a `go` decision,
  145. establish a project constitution if needed, then pass the handoff summary from
  146. `decision.md` to `/speckit-specify`. Stopping with a documented reason is also a
  147. useful outcome.
  148. [Assessment walkthrough](https://github.github.io/spec-kit/guides/assessment.html) ·
  149. [Command reference](https://github.github.io/spec-kit/reference/agentic-assessment.html)
  150. <a id="-making-spec-kit-your-own-extensions--presets"></a>
  151. <a id="-bundles-role-based-setups"></a>
  152. <a id="-community"></a>
  153. ## Customize or bring your own process
  154. Customize Spec-Driven Development, bug fixing, or idea assessment to fit your
  155. team's standards. Or bring your own process without adopting any of them.
  156. Combine the [capabilities above](#capabilities) to match your goal:
  157. - Adapt an existing process with a preset, such as requiring regulatory traceability in plans. Use a project-local override for a one-off template change.
  158. - Bring your own process by adding its commands through an extension and exposing them to your coding agent through an integration.
  159. - Automate commands and checks in a workflow. Use overlays to adapt an installed workflow without forking it, or add custom workflow steps when the built-in types are not enough.
  160. - Share a reusable setup by packaging its extensions, presets, workflows, and workflow steps in a bundle.
  161. Start with the smallest change that meets your needs; you do not have to replace
  162. the whole process.
  163. [Customization guide](https://github.github.io/spec-kit/how-to/customization.html) ·
  164. [Community components and walkthroughs](https://github.github.io/spec-kit/community/overview.html)
  165. <a id="-specify-cli-reference"></a>
  166. <a id="available-slash-commands"></a>
  167. <a id="-learn-more"></a>
  168. <a id="-core-philosophy"></a>
  169. <a id="-development-phases"></a>
  170. <a id="-experimental-goals"></a>
  171. <a id="-does-spec-kit-use-spec-kit"></a>
  172. ## Documentation
  173. - [CLI reference](https://github.github.io/spec-kit/index.html#specify-cli) and [process commands](https://github.github.io/spec-kit/reference/agentic-sdd.html#command-overview)
  174. - [How-to guides](https://github.github.io/spec-kit/how-to/index.html) for applying Spec Kit to your project work
  175. - [SDD philosophy](https://github.github.io/spec-kit/how-to/sdd.html), [full methodology](./spec-driven.md), and [evolving existing specs](https://github.github.io/spec-kit/how-to/evolving-specs.html)
  176. - [Project history](https://github.github.io/spec-kit/overview/history.html)
  177. - [How Spec Kit uses Spec Kit](./CONTRIBUTING.md#does-spec-kit-use-spec-kit)
  178. ## In the news
  179. - [Open Source Friday: Spec Kit Part 2](https://www.youtube.com/watch?v=8hHCpNVLhmI) (October 16, 2026) — Manfred Riem and Nicole Haugen discuss Spec Kit 1.0 and the expanded toolkit.
  180. - [Living Specs in SpecKit](https://www.alfredo-perez.dev/blog/2026-10-15-living-specs) (October 15, 2026) — Alfredo Perez explores maintaining capability-level specifications as a project evolves.
  181. - [Spec Kit Customization Series](https://jesseliberty.com/2026/10/08/4-solutions-to-spec-kit-issues/) (October 8–10, 2026) — Jesse Liberty walks through presets and extension authoring, including testing and publishing.
  182. - [From Spec-First to Enterprise-Ready: Extending GitHub Spec Kit](https://developer.microsoft.com/blog/from-spec-first-to-enterprise-ready-extending-github-spec-kit/) (October 7, 2026) — Apoorv Gupta explains enterprise customization through presets, extensions, bundles, workflows, and governed catalogs.
  183. - [Open Source Friday with Spec Kit](https://www.youtube.com/watch?v=2IArMAhkJcE) (May 8, 2026) — An introduction and SDD demonstration with Manfred Riem.
  184. ## Star history
  185. <p align="center">
  186. <a href="https://www.star-history.com/#github/spec-kit&Date">
  187. <picture>
  188. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=github%2Fspec-kit&type=Date&theme=dark"/>
  189. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=github%2Fspec-kit&type=Date"/>
  190. <img src="https://api.star-history.com/svg?repos=github%2Fspec-kit&type=Date" alt="Spec Kit star history chart"/>
  191. </picture>
  192. </a>
  193. </p>
  194. <p align="center">
  195. <em>Thanks to everyone who helps Spec Kit shine.</em>
  196. </p>
  197. <a id="-support"></a>
  198. ## Support and contributing
  199. [Report a bug or request a feature](https://github.com/github/spec-kit/issues/new) ·
  200. [Contributing guide](./CONTRIBUTING.md) · [Code of conduct](./CODE_OF_CONDUCT.md)
  201. <a id="-license"></a>
  202. Spec Kit is [MIT licensed](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.