You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+60-55Lines changed: 60 additions & 55 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -289,7 +289,6 @@ Community projects that extend, visualize, or build on Spec Kit:
289
289
-**[SpecKit Companion](https://marketplace.visualstudio.com/items?itemName=alfredoperez.speckit-companion)** — A VS Code extension that brings a visual GUI to Spec Kit. Browse specs in a rich markdown viewer with clickable file references, create specifications with image attachments, comment and refine each step inline (GitHub-style review), track your progress through the SDD workflow with a visual phase stepper, and manage steering documents like constitutions and templates.
@@ -321,22 +320,63 @@ Community projects that extend, visualize, or build on Spec Kit:
321
320
|[Trae](https://www.trae.ai/)| ✅ ||
322
321
| Generic | ✅ | Bring your own agent — use `--ai generic --ai-commands-dir <path>` for unsupported agents |
323
322
323
+
## Available Slash Commands
324
+
325
+
After running `specify init`, your AI coding agent will have access to these slash commands for structured development. If you pass `--ai <agent> --ai-skills`, Spec Kit installs agent skills instead of slash-command prompt files; `--ai-skills` requires `--ai`.
326
+
327
+
#### Core Commands
328
+
329
+
Essential commands for the Spec-Driven Development workflow:
After running `specify init`, your AI coding agent will have access to these structured development commands.
439
-
440
-
Most agents expose the traditional dotted slash commands shown below, like `/speckit.plan`.
441
-
442
-
Claude Code installs spec-kit as skills and invokes them as `/speckit-constitution`, `/speckit-specify`, `/speckit-plan`, `/speckit-tasks`, and `/speckit-implement`.
443
-
444
-
For Codex CLI, `--ai-skills` installs spec-kit as agent skills instead of slash-command prompt files. In Codex skills mode, invoke spec-kit as `$speckit-constitution`, `$speckit-specify`, `$speckit-plan`, `$speckit-tasks`, and `$speckit-implement`.
445
-
446
-
#### Core Commands
447
-
448
-
Essential commands for the Spec-Driven Development workflow:
|`/speckit.clarify`| Clarify underspecified areas (recommended before `/speckit.plan`; formerly `/quizme`) |
465
-
|`/speckit.analyze`| Cross-artifact consistency & coverage analysis (run after `/speckit.tasks`, before `/speckit.implement`) |
466
-
|`/speckit.checklist`| Generate custom quality checklists that validate requirements completeness, clarity, and consistency (like "unit tests for English") |
467
-
468
476
### Environment Variables
469
477
470
478
| Variable | Description |
@@ -475,21 +483,18 @@ Additional commands for enhanced quality and validation:
475
483
476
484
Spec Kit can be tailored to your needs through two complementary systems — **extensions** and **presets** — plus project-local overrides for one-off adjustments:
**Templates** are resolved at **runtime** — Spec Kit walks the stack top-down and uses the first match. Project-local overrides (`.specify/templates/overrides/`) let you make one-off adjustments for a single project without creating a full preset. **Commands** are applied at **install time** — when you run `specify extension add` or `specify preset add`, command files are written into agent directories (e.g., `.claude/commands/`). If multiple presets or extensions provide the same command, the highest-priority version wins. On removal, the next-highest-priority version is restored automatically. If no overrides or customizations exist, Spec Kit uses its core defaults.
-**Templates** are resolved at **runtime** — Spec Kit walks the stack top-down and uses the first match.
494
+
- Project-local overrides (`.specify/templates/overrides/`) let you make one-off adjustments for a single project without creating a full preset.
495
+
-**Extension/preset commands** are applied at **install time** — when you run `specify extension add` or `specify preset add`, command files are written into agent directories (e.g., `.claude/commands/`).
496
+
- If multiple presets or extensions provide the same command, the highest-priority version wins. On removal, the next-highest-priority version is restored automatically.
497
+
- If no overrides or customizations exist, Spec Kit uses its core defaults.
0 commit comments