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: AGENTS.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -381,25 +381,26 @@ Implementation: Extends `YamlIntegration` (parallel to `TomlIntegration`):
381
381
382
382
## Branch Naming Convention
383
383
384
-
All branches **must** follow this pattern:
384
+
Branches follow one of two patterns depending on whether an issue exists:
385
385
386
386
```
387
-
<type>/<number>-<short-slug>
387
+
<type>/<number>-<short-slug> # when an issue is created first
388
+
<type>/<short-slug> # when no issue exists (PR-only changes)
388
389
```
389
390
390
-
Where `<number>` is either an issue number or a PR number — whichever is created first.
391
+
When an issue exists, include its number immediately after the prefix — this is what makes branches traceable. For small or self-contained changes that go straight to a PR without a tracking issue, omit the number.
391
392
392
393
| Prefix | When to use | Example |
393
394
|---|---|---|
394
395
| `feat/` | New features | `feat/2342-workflow-cli-alignment` |
@@ -581,7 +581,7 @@ Once the implementation is complete, test the application and resolve any runtim
581
581
582
582
---
583
583
584
-
## Support
584
+
## 💬 Support
585
585
586
586
For support, please open a [GitHub issue](https://github.com/github/spec-kit/issues/new). We welcome bug reports, feature requests, and questions about using Spec-Driven Development.
Copy file name to clipboardExpand all lines: docs/community/extensions.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The following community-contributed extensions are available in [`catalog.commun
27
27
| AI-Driven Engineering (AIDE) | A structured 7-step workflow for building new projects from scratch with AI assistants — from vision through implementation |`process`| Read+Write |[aide](https://github.com/mnriem/spec-kit-extensions/tree/main/aide)|
28
28
| API Evolve | Managed API contract evolution — breaking-change detection, semver enforcement, deprecation orchestration, and lifecycle gates across REST, GraphQL, and gRPC |`process`| Read+Write |[spec-kit-api-evolve](https://github.com/Quratulain-bilal/spec-kit-api-evolve)|
29
29
| Architect Impact Previewer | Predicts architectural impact, complexity, and risks of proposed changes before implementation. |`visibility`| Read-only |[spec-kit-architect-preview](https://github.com/UmmeHabiba1312/spec-kit-architect-preview)|
30
-
| Architecture Guard |Continuous architecture governance for AI-assisted development. Reviews specs, plans, and code for architecture drift, producing structured refactor tasks and evolution proposals.|`process`| Read+Write |[spec-kit-architecture-guard](https://github.com/DyanGalih/spec-kit-architecture-guard)|
30
+
| Architecture Guard |Framework-agnostic architecture review extension for validating implementation against governance and architecture constitutions, detecting architectural drift, and generating non-blocking refactor tasks |`process`| Read+Write |[spec-kit-architecture-guard](https://github.com/DyanGalih/spec-kit-architecture-guard)|
31
31
| Architecture Workflow | Generate or reverse project-level 4+1 architecture view artifacts and synthesis |`docs`| Read+Write |[spec-kit-arch](https://github.com/bigsmartben/spec-kit-arch)|
32
32
| Archive Extension | Archive merged features into main project memory. |`docs`| Read+Write |[spec-kit-archive](https://github.com/stn1slv/spec-kit-archive)|
33
33
| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication |`integration`| Read+Write |[spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops)|
@@ -78,6 +78,7 @@ The following community-contributed extensions are available in [`catalog.commun
78
78
| PR Bridge | Auto-generate pull request descriptions, checklists, and summaries from spec artifacts |`process`| Read-only |[spec-kit-pr-bridge-](https://github.com/Quratulain-bilal/spec-kit-pr-bridge-)|
79
79
| Presetify | Create and validate presets and preset catalogs |`process`| Read+Write |[presetify](https://github.com/mnriem/spec-kit-extensions/tree/main/presetify)|
80
80
| Product Forge | Full product lifecycle from research to release — portfolio, lite mode, monorepo, optional V-Model |`process`| Read+Write |[speckit-product-forge](https://github.com/VaiYav/speckit-product-forge)|
81
+
| Product Spec Extension | Generates PRFAQ, Lean PRD, stakeholder summaries, and technical designs from engineering specs |`docs`| Read+Write |[spec-kit-product](https://github.com/d0whc3r/spec-kit-product)|
81
82
| Project Health Check | Diagnose a Spec Kit project and report health issues across structure, agents, features, scripts, extensions, and git |`visibility`| Read-only |[spec-kit-doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor)|
82
83
| Project Status | Show current SDD workflow progress — active feature, artifact status, task completion, workflow phase, and extensions summary |`visibility`| Read-only |[spec-kit-status](https://github.com/KhawarHabibKhan/spec-kit-status)|
83
84
| QA Testing Extension | Systematic QA testing with browser-driven or CLI-based validation of acceptance criteria from spec |`code`| Read-only |[spec-kit-qa](https://github.com/arunt14/spec-kit-qa)|
@@ -115,6 +116,7 @@ The following community-contributed extensions are available in [`catalog.commun
115
116
| Team Assign | Assign tasks.md items to human engineers, split into subtasks, and generate a per-engineer workboard |`process`| Read+Write |[spec-kit-team-assign](https://github.com/tarunkumarbhati/spec-kit-team-assign)|
116
117
| Time Machine | Retroactively apply the full SDD workflow to existing codebases — analyse, spec, and ship feature-by-feature |`process`| Read+Write |[spec-kit-time-machine](https://github.com/teeyo/spec-kit-time-machine)|
117
118
| TinySpec | Lightweight single-file workflow for small tasks — skip the heavy multi-step SDD process |`process`| Read+Write |[spec-kit-tinyspec](https://github.com/Quratulain-bilal/spec-kit-tinyspec)|
| Token Consumption Analyzer | Captures, analyzes, and compares token consumption across SDD workflows |`visibility`| Read-only |[spec-kit-token-analyzer](https://github.com/coderandhiker/spec-kit-token-analyzer)|
119
121
| V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability |`docs`| Read+Write |[spec-kit-v-model](https://github.com/leocamello/spec-kit-v-model)|
120
122
| Verify Extension | Post-implementation quality gate that validates implemented code against specification artifacts |`code`| Read-only |[spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify)|
Copy file name to clipboardExpand all lines: docs/community/presets.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,17 +15,18 @@ The following community-contributed presets customize how Spec Kit behaves — o
15
15
| Claude AskUserQuestion | Upgrades `/speckit.clarify` and `/speckit.checklist` on Claude Code from Markdown-table prompts to the native AskUserQuestion picker, with a recommended option and reasoning on every question | 2 commands | — |[spec-kit-preset-claude-ask-questions](https://github.com/0xrafasec/spec-kit-preset-claude-ask-questions)|
| Explicit Task Dependencies | Adds explicit `(depends on T###)` dependency declarations and an Execution Wave DAG to tasks.md for parallel scheduling | 1 template, 1 command | — |[spec-kit-preset-explicit-task-dependencies](https://github.com/Quratulain-bilal/spec-kit-preset-explicit-task-dependencies)|
18
-
| Fiction Book Writing | It adapts the Spec-Driven Development workflow for storytelling to create books or audiobooks (with annotations) in 12 languages: features become story elements, specs become story briefs, plans become story structures, and tasks become scene-by-scene writing tasks. Supports single and multi-POV, all major plot structure frameworks, and two style modes: an author voice sample or humanized AI prose. Supports interactive elements like brainstorming, interview, roleplay and extras like statistics, cover builder and bio command. Export with templates for KDP, D2D etc. |22 templates, 27 commands, 2 scripts | — |[speckit-preset-fiction-book-writing](https://github.com/adaumann/speckit-preset-fiction-book-writing)|
18
+
| Fiction Book Writing | It adapts the Spec-Driven Development workflow for storytelling to create books or audiobooks (with annotations) in 12 languages: features become story elements, specs become story briefs, plans become story structures, and tasks become scene-by-scene writing tasks. Supports single and multi-POV, all major plot structure frameworks, and two style modes: an author voice sample or humanized AI prose principles. Supports interactive elements like brainstorming, interview, roleplay and extras like statistics, cover builder and bio command. Export with templates for KDP, D2D etc. |25 templates, 33 commands, 2 scripts | — |[speckit-preset-fiction-book-writing](https://github.com/adaumann/speckit-preset-fiction-book-writing)|
19
19
| Game Narrative Writing | Spec-Driven Development for interactive game narrative pre-production for video games. Authors write in a portable generic format, Twine/Sugarcube (.twee) or Ink (.ink). Covers choice-IF, visual novels, and branching dialogue. Supports Tier 1 mechanic hooks (flag, counter, inventory, timer, trust, currency, npc_state, ending_condition), multi-ending design, series carry-over variable registry, and NPC-focused character architecture. | 22 templates, 36 commands, 2 scripts | — |[speckit-preset-game-narrative-writing](https://github.com/adaumann/speckit-preset-game-narrative-writing)|
20
20
| iSAQB Architecture Governance | Adds general iSAQB/CPSA-F and arc42 architecture governance: goals, context, building blocks, runtime and deployment views, quality scenarios, ADRs, risks, and technical debt | 13 templates, 3 commands | — |[spec-kit-preset-isaqb-architecture-governance](https://github.com/hindermath/spec-kit-preset-isaqb-architecture-governance)|
21
21
| Jira Issue Tracking | Overrides `speckit.taskstoissues` to create Jira epics, stories, and tasks instead of GitHub Issues via Atlassian MCP tools | 1 command | — |[spec-kit-preset-jira](https://github.com/luno/spec-kit-preset-jira)|
22
22
| Model Driven Engineering | Focuses on streamlined commands, app repository support, cross-spec support, and capability-aware project memory for model-driven engineering workflows | 6 templates, 11 commands | MDE extension |[spec-kit-preset-mde](https://github.com/AI-MDE/spec-kit-preset-mde)|
23
23
| Multi-Repo Branching | Coordinates feature branch creation across multiple git repositories (independent repos and submodules) during plan and tasks phases | 2 commands | — |[spec-kit-preset-multi-repo-branching](https://github.com/sakitA/spec-kit-preset-multi-repo-branching)|
24
24
| Pirate Speak (Full) | Transforms all Spec Kit output into pirate speak — specs become "Voyage Manifests", plans become "Battle Plans", tasks become "Crew Assignments" | 6 templates, 9 commands | — |[spec-kit-presets](https://github.com/mnriem/spec-kit-presets)|
25
25
| Screenwriting | Spec-Driven Development for screenwriting/scriptwriting/tutorials: feature films, television (pilot, episode, limited series), and stage plays. Adapts the Spec Kit workflow to screenplay craft — slug lines, action lines, act breaks, beat sheets, and industry-standard pitch documents. Supports three-act, Save the Cat, TV pilot, network episode, cable/streaming episode, and stage-play structural frameworks. Export to Fountain, FTX, PDF | 26 templates, 32 commands, 1 script | — |[speckit-preset-screenwriting](https://github.com/adaumann/speckit-preset-screenwriting)|
26
-
| Security Governance | Adds secure development governance: memory-safe-language preference, secure code generation, NIST SSDF, CWE Top 25, OWASP ASVS, SBOM/VEX/SLSA, OpenSSF Scorecard, and EU CRA applicability | 12 templates, 3 commands | — |[spec-kit-preset-security-governance](https://github.com/hindermath/spec-kit-preset-security-governance)|
26
+
| Security Governance | Adds secure development governance: memory-safe-language preference, secure code generation, NIST SSDF, CWE Top 25, OWASP ASVS, SBOM/AI-SBOM, VEX/SLSA, OpenSSF Scorecard, G7/BSI AI-SBOM target evidence, and EU CRA applicability | 12 templates, 3 commands | — |[spec-kit-preset-security-governance](https://github.com/hindermath/spec-kit-preset-security-governance)|
27
27
| Spec2Cloud | Spec-driven workflow tuned for shipping to Azure: spec → plan → tasks → implement → deploy | 5 templates, 8 commands | — |[spec2cloud](https://github.com/Azure-Samples/Spec2Cloud)|
28
28
| Table of Contents Navigation | Adds a navigable Table of Contents to generated spec.md, plan.md, and tasks.md documents | 3 templates, 3 commands | — |[spec-kit-preset-toc-navigation](https://github.com/Quratulain-bilal/spec-kit-preset-toc-navigation)|
29
29
| VS Code Ask Questions | Enhances the clarify command to use `vscode/askQuestions` for batched interactive questioning. | 1 command | — |[spec-kit-presets](https://github.com/fdcastel/spec-kit-presets)|
Copy file name to clipboardExpand all lines: docs/index.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Run `specify init` with your agent of choice and Spec Kit sets up the right comm
43
43
44
44
### Make it your own
45
45
46
-
<spanclass="pillar-stat">91 community extensions</span> (50+ authors), <spanclass="pillar-stat">18 presets</span>, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, or replace it entirely. Build and publish your own.
46
+
<spanclass="pillar-stat">105 community extensions</span> (60+ authors), <spanclass="pillar-stat">22 presets</span>, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, or replace it entirely. Build and publish your own.
47
47
48
48
Including entirely different SDD processes:
49
49
@@ -82,7 +82,7 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a
82
82
83
83
<divclass="stats-grid">
84
84
<divclass="stat-item">
85
-
<span class="stat-number">96K+</span>
85
+
<span class="stat-number">106K+</span>
86
86
<span class="stat-label">GitHub stars</span>
87
87
</div>
88
88
<divclass="stat-item">
@@ -94,11 +94,11 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a
Copy file name to clipboardExpand all lines: docs/install/pipx.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Installing with pipx
2
2
3
-
[pipx](https://pypa.github.io/pipx/) is a tool for installing Python CLI applications in isolated environments. It does not require [uv](https://docs.astral.sh/uv/).
3
+
[pipx](https://pipx.pypa.io/) is a tool for installing Python CLI applications in isolated environments. It does not require [uv](https://docs.astral.sh/uv/).
0 commit comments