33
stars
8
commits
Jul 7, 2026
updated
A Spec Kit extension that adds a structured bugfix workflow — capture bugs discovered during implementation, trace them to spec artifacts, and surgically patch specs without regenerating from scratch.
When bugs surface during implementation, the SDD workflow breaks down:
The Bugfix Workflow extension adds four commands that close the gap between bug discovery and spec correction:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.bugfix.report | Capture a bug and trace it back to the relevant spec, plan, and task artifacts | Yes — creates bug report file |
/speckit.bugfix.patch | Surgically update spec, plan, and tasks to address the reported bug | Yes — spec.md, plan.md, tasks.md |
/speckit.bugfix.switch | Switch to a different bugfix context | Yes |
/speckit.bugfix.verify | Verify that bugfix patches are consistent across all spec artifacts | No — read-only |
specify extension add bugfix --from https://github.com/Quratulain-bilal/spec-kit-bugfix/archive/refs/tags/v1.1.0.zip
The extension classifies bugs into five categories:
| Type | Description | Example |
|---|---|---|
| Spec gap | Requirement missing from spec | Auth flow doesn't handle expired tokens |
| Spec conflict | Two requirements contradict | "Must be stateless" vs "Must track sessions" |
| Implementation drift | Code diverges from spec | Spec says REST, code uses GraphQL |
| Untested flow | Edge case not covered | Concurrent user updates not handled |
| Dependency issue | External dependency changed | API response format differs from assumption |
Bug discovered during /speckit.implement
│
▼
/speckit.bugfix.report ← Capture bug, trace to artifacts, classify
│
▼
/speckit.bugfix.patch ← Surgically update spec, plan, tasks
│
▼
/speckit.bugfix.verify ← Confirm all artifacts are consistent
│
▼
/speckit.implement ← Resume implementation with corrected specs
Use /speckit.bugfix.switch <spec-id> if the bug is discovered after the feature branch has been destroyed.
/speckit.bugfix.reportCaptures a bug and produces a structured report with full artifact traceability:
specs/{feature}/bugs/BUG-{NNN}.md/speckit.bugfix.patchSurgically updates spec artifacts based on a bug report:
(reopened — BUG-NNN) annotation/speckit.bugfix.switchSwitches the active bugfix context when working with multiple bugs:
/speckit.bugfix.verifyRead-only consistency check after patching:
The extension registers an optional hook:
/bugfix Slash Command (25+ upvotes, maintainer-approved as extension)MIT
33
stars
8
commits
Jul 7, 2026
updated
A Spec Kit extension that adds a structured bugfix workflow — capture bugs discovered during implementation, trace them to spec artifacts, and surgically patch specs without regenerating from scratch.
When bugs surface during implementation, the SDD workflow breaks down:
The Bugfix Workflow extension adds four commands that close the gap between bug discovery and spec correction:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.bugfix.report | Capture a bug and trace it back to the relevant spec, plan, and task artifacts | Yes — creates bug report file |
/speckit.bugfix.patch | Surgically update spec, plan, and tasks to address the reported bug | Yes — spec.md, plan.md, tasks.md |
/speckit.bugfix.switch | Switch to a different bugfix context | Yes |
/speckit.bugfix.verify | Verify that bugfix patches are consistent across all spec artifacts | No — read-only |
specify extension add bugfix --from https://github.com/Quratulain-bilal/spec-kit-bugfix/archive/refs/tags/v1.1.0.zip
The extension classifies bugs into five categories:
| Type | Description | Example |
|---|---|---|
| Spec gap | Requirement missing from spec | Auth flow doesn't handle expired tokens |
| Spec conflict | Two requirements contradict | "Must be stateless" vs "Must track sessions" |
| Implementation drift | Code diverges from spec | Spec says REST, code uses GraphQL |
| Untested flow | Edge case not covered | Concurrent user updates not handled |
| Dependency issue | External dependency changed | API response format differs from assumption |
Bug discovered during /speckit.implement
│
▼
/speckit.bugfix.report ← Capture bug, trace to artifacts, classify
│
▼
/speckit.bugfix.patch ← Surgically update spec, plan, tasks
│
▼
/speckit.bugfix.verify ← Confirm all artifacts are consistent
│
▼
/speckit.implement ← Resume implementation with corrected specs
Use /speckit.bugfix.switch <spec-id> if the bug is discovered after the feature branch has been destroyed.
/speckit.bugfix.reportCaptures a bug and produces a structured report with full artifact traceability:
specs/{feature}/bugs/BUG-{NNN}.md/speckit.bugfix.patchSurgically updates spec artifacts based on a bug report:
(reopened — BUG-NNN) annotation/speckit.bugfix.switchSwitches the active bugfix context when working with multiple bugs:
/speckit.bugfix.verifyRead-only consistency check after patching:
The extension registers an optional hook:
/bugfix Slash Command (25+ upvotes, maintainer-approved as extension)MIT