+
+
# GitHub Spec Kit
**Spec-Driven Development or your own process — step by step or as an automated workflow.**
@@ -31,7 +33,7 @@ Define what to build before building it. Rich templates, quality checklists, and
### Use any coding agent
-35 integrations — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
+38 integrations — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
Run `specify init` with your agent of choice and Spec Kit sets up the right command files and directory structures automatically. If your agent isn't listed, the `generic` integration is an escape hatch for any tool.
@@ -43,7 +45,7 @@ Run `specify init` with your agent of choice and Spec Kit sets up the right comm
### Make it your own
-138 community extensions (70+ authors), 25 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, and package it all up as bundles you can share — or replace the process entirely. The process itself lives in these building blocks, so you're never locked to SDD, or even to software.
+157 community extensions (90+ authors), 33 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, and package it all up as bundles you can share — or replace the process entirely. The process itself lives in these building blocks, so you're never locked to SDD, or even to software.
Including entirely different processes:
@@ -105,31 +107,31 @@ Spec-Driven Development is built upon the [Agentic SDLC 12 Factors](https://tika
## Built by the community
-**240+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new processes. Anyone can create and publish an extension, preset, or workflow.
+**270+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new processes. Anyone can create and publish an extension, preset, or workflow.
@@ -147,6 +149,14 @@ Spec-Driven Development is built upon the [Agentic SDLC 12 Factors](https://tika
Getting Started
Install, configure, and run your first SDD workflow
+
+ Existing Projects
+ Adopt Spec Kit safely in an established codebase
+
+
+ Upgrade
+ Keep an existing Spec Kit project current across releases
+
Reference
Core commands, integrations, extensions, presets, and workflows
@@ -163,6 +173,10 @@ Spec-Driven Development is built upon the [Agentic SDLC 12 Factors](https://tika
What is SDD?
The philosophy behind Spec-Driven Development
+
+ History
+ How Spec Kit grew from its SDD foundation into an extensible process harness
+
---
@@ -178,4 +192,4 @@ Ready to start? Follow the [Quick Start Guide](quickstart.md).
-
+
# GitHub Spec Kit
**Spec-Driven Development or your own process — step by step or as an automated workflow.**
@@ -31,7 +33,7 @@ Define what to build before building it. Rich templates, quality checklists, and
### Use any coding agent
-35 integrations — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
+38 integrations — Copilot, Gemini, Codex, Kilo Code, Zed, Claude, Forge, Kiro, and more. Switch freely between agents with a single command. No lock-in.
Run `specify init` with your agent of choice and Spec Kit sets up the right command files and directory structures automatically. If your agent isn't listed, the `generic` integration is an escape hatch for any tool.
@@ -43,7 +45,7 @@ Run `specify init` with your agent of choice and Spec Kit sets up the right comm
### Make it your own
-138 community extensions (70+ authors), 25 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, and package it all up as bundles you can share — or replace the process entirely. The process itself lives in these building blocks, so you're never locked to SDD, or even to software.
+157 community extensions (90+ authors), 33 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, and package it all up as bundles you can share — or replace the process entirely. The process itself lives in these building blocks, so you're never locked to SDD, or even to software.
Including entirely different processes:
@@ -105,31 +107,31 @@ Spec-Driven Development is built upon the [Agentic SDLC 12 Factors](https://tika
## Built by the community
-**240+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new processes. Anyone can create and publish an extension, preset, or workflow.
+**270+ contributors** power the Spec Kit ecosystem — from core integrations to entirely new processes. Anyone can create and publish an extension, preset, or workflow.
- 121K+
+ 130K+
GitHub stars
- 240+
+ 270+
Contributors
- 35
+ 38
Integrations
- 138
+ 157
Extensions
- 25
+ 33
Presets
- 6
+ 7
Friends projects
Last updated: July 16, 2026
+Last updated: August 21, 2026
diff --git a/docs/local-development.md b/docs/local-development.md index 22e08fbbe7..34070451fc 100644 --- a/docs/local-development.md +++ b/docs/local-development.md @@ -2,7 +2,7 @@ This guide shows how to iterate on the `specify` CLI locally without publishing a release or committing to `main` first. -> Scripts are available as Bash (`.sh`), PowerShell (`.ps1`), and Python (`.py`) variants. Interactive `specify init` prompts you to choose one; non-interactive runs default to a shell variant for your OS. Pass `--script sh|ps|py` to select explicitly. +> Scripts are available as Bash (`.sh`), PowerShell (`.ps1`), and Python (`.py`) variants. Interactive `specify init` prompts you to choose one; non-interactive runs (no TTY, or `--non-interactive`) default to a shell variant for your OS. Pass `--script sh|ps|py` to select explicitly. ## 1. Clone and Switch Branches diff --git a/docs/quickstart.md b/docs/quickstart.md index 4d4eaf89e0..fb2ecc2f74 100644 --- a/docs/quickstart.md +++ b/docs/quickstart.md @@ -3,7 +3,7 @@ This guide will help you get started with Spec-Driven Development using Spec Kit. Throughout, we illustrate each step with a running example: **Taskify**, a small team productivity platform. > [!NOTE] -> Automation scripts are provided as Bash (`.sh`), PowerShell (`.ps1`), and Python (`.py`) variants. Interactive `specify init` prompts you to choose one; non-interactive runs default to a shell variant for your OS. Pass `--script sh|ps|py` to select explicitly. +> Automation scripts are provided as Bash (`.sh`), PowerShell (`.ps1`), and Python (`.py`) variants. Interactive `specify init` prompts you to choose one; non-interactive runs (no TTY, or `--non-interactive`) default to a shell variant for your OS. Pass `--script sh|ps|py` to select explicitly. Commands are shown here in `/speckit.*` form, but the exact invocation depends on your agent. Some skills-based agents use `$speckit-*` (e.g. Codex, ZCode) or `/skill:speckit-*` (e.g. Kimi). Use whichever form your agent exposes — the steps are otherwise identical. @@ -43,10 +43,13 @@ uv tool install specify-cli specify init taskify # or: specify init . to use the current directory ``` -`init` lets you pick your coding agent interactively, or pass it explicitly with `--integration` (e.g. `--integration copilot`). +`init` lets you pick your coding agent interactively, or pass it explicitly with `--integration` (e.g. `--integration copilot`). For CI and AI agent harnesses, add `--non-interactive` so unspecified choices use documented defaults instead of hanging on an arrow-key picker. > [!NOTE] > Prefer `pipx`, one-time `uvx` runs, a pinned release, or an offline/air-gapped setup? See the [Installation Guide](installation.md) for all supported methods. +> Adding Spec Kit to a repository that already contains code? Follow +> [Adopting Spec Kit in an Existing Project](guides/existing-projects.md) before +> starting the workflow below. ### Step 1: `/speckit.constitution` — set the ground rules diff --git a/docs/reference/extensions.md b/docs/reference/extensions.md index 919617a087..0473e72008 100644 --- a/docs/reference/extensions.md +++ b/docs/reference/extensions.md @@ -75,6 +75,8 @@ specify extension update [