23
stars
2
commits
Apr 7, 2026
updated
A Spec Kit extension that enables iterative specification refinement — update specs in-place, propagate changes to downstream artifacts, and track sync status across the SDD lifecycle.
Spec Kit's /speckit.specify command is optimized for creating new specifications, but real-world development requires continuous iteration. When requirements change mid-implementation, teams face:
The Refine extension adds four commands that close the iteration gap:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.refine.update | Update spec.md in-place based on new requirements or feedback | Yes — spec.md |
/speckit.refine.propagate | Cascade spec changes to plan.md and tasks.md | Yes — plan.md, tasks.md |
/speckit.refine.diff | Preview impact of spec changes before propagating | No — read-only |
/speckit.refine.status | Show sync status between spec, plan, and tasks | No — read-only |
specify extension add --from https://github.com/Quratulain-bilal/spec-kit-refine/archive/refs/tags/v1.0.0.zip
Requirements change
│
▼
/speckit.refine.update ← Update spec.md in-place
│
▼
/speckit.refine.diff ← Preview downstream impact (optional)
│
▼
/speckit.refine.propagate ← Cascade changes to plan.md & tasks.md
│
▼
/speckit.refine.status ← Verify all artifacts are in sync
/speckit.refine.updateUpdates an existing spec.md without creating a new feature branch. Handles:
/speckit.refine.propagateSurgically updates plan.md and tasks.md to reflect spec changes:
/speckit.refine.diffRead-only impact analysis before propagating:
/speckit.refine.statusDashboard showing artifact synchronization:
The extension registers optional hooks:
MIT
2 commits
23
stars
2
commits
Apr 7, 2026
updated
A Spec Kit extension that enables iterative specification refinement — update specs in-place, propagate changes to downstream artifacts, and track sync status across the SDD lifecycle.
Spec Kit's /speckit.specify command is optimized for creating new specifications, but real-world development requires continuous iteration. When requirements change mid-implementation, teams face:
The Refine extension adds four commands that close the iteration gap:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.refine.update | Update spec.md in-place based on new requirements or feedback | Yes — spec.md |
/speckit.refine.propagate | Cascade spec changes to plan.md and tasks.md | Yes — plan.md, tasks.md |
/speckit.refine.diff | Preview impact of spec changes before propagating | No — read-only |
/speckit.refine.status | Show sync status between spec, plan, and tasks | No — read-only |
specify extension add --from https://github.com/Quratulain-bilal/spec-kit-refine/archive/refs/tags/v1.0.0.zip
Requirements change
│
▼
/speckit.refine.update ← Update spec.md in-place
│
▼
/speckit.refine.diff ← Preview downstream impact (optional)
│
▼
/speckit.refine.propagate ← Cascade changes to plan.md & tasks.md
│
▼
/speckit.refine.status ← Verify all artifacts are in sync
/speckit.refine.updateUpdates an existing spec.md without creating a new feature branch. Handles:
/speckit.refine.propagateSurgically updates plan.md and tasks.md to reflect spec changes:
/speckit.refine.diffRead-only impact analysis before propagating:
/speckit.refine.statusDashboard showing artifact synchronization:
The extension registers optional hooks:
MIT
2 commits