Repository navigation
Releases
spec-kit-epic 0.1.5
A Spec Kit extension for work too big for one feature: five commands (specify, plan, cut, review, close) that break an epic into features, deliver them in order, and keep the decisions made along the way holding across all of them. Requires Spec Kit 0.12.9 to 1.1.x and git.
Install
specify extension add --from https://github.com/pmckeown/spec-kit-epic/archive/refs/tags/v0.1.5.zipThe extension is not yet in a Spec Kit catalogue, so specify asks you to confirm the source. See the README for upgrading.
0.1.5
- After a cut with open decisions, an
openentry beyond corespecify's clarification-marker limit is cited in the requirement text, not guessed. cutnames a feature branch the way the epic's earlier cuts were named, or for the first cut, like the project's most recent feature branches.- The README says stale branches count towards the next feature number.
- A seeded pointer for a
provisionalentry starts withPROVISIONAL:. - New
status_notemarkerGATE SETTLES UNGROUNDED, written whencutlets a gate through that settles its own[UNGROUNDED]premise;reviewchecks the mark is grounded once the gate is observed.
Earlier changes are in CHANGELOG.md.
spec-kit-epic 0.1.4
A Spec Kit extension for work too big for one feature: five commands (specify, plan, cut, review, close) that break an epic into features, deliver them in order, and keep the decisions made along the way holding across all of them. Requires Spec Kit 0.12.9 to 1.1.x and git.
Install
specify extension add --from https://github.com/pmckeown/spec-kit-epic/archive/refs/tags/v0.1.4.zipThe extension is not yet in a Spec Kit catalogue, so specify asks you to confirm the source. See the README for upgrading.
0.1.4
FORMATS.mdhas seeded-pointer shapes for every entry type:decision,discoveryandopenjoinrefusalanddeferral.- New
status_notemarkerCUT WITH OPEN DECISIONS, written when the owner cuts past refusal 10;reviewtreats each id stillopenas an owner's call. cutnumbers a sequential feature after the highestspecs/NNN-*on any branch, not only the target, so parallel cuts do not collide.cutcreates a missing target from the branch that holds the epic, which must be the current branch.cutsays thatspec.mdand corespecify's other output, such aschecklists/, stay uncommitted for the human's review.cuttells corespecifyto keepEFand decision citations but leave the gate's mechanism to coreplan.- After a cut with open decisions, core
specify's clarification questions are answered by pointing to theopenentries, not settled in the spec.
Earlier changes are in CHANGELOG.md.
spec-kit-epic 0.1.3
A Spec Kit extension for work too big for one feature: five commands (specify, plan, cut, review, close) that break an epic into features, deliver them in order, and keep the decisions made along the way holding across all of them. Requires Spec Kit 0.12.9 to 1.1.x and git.
Install
specify extension add --from https://github.com/pmckeown/spec-kit-epic/archive/refs/tags/v0.1.3.zipThe extension is not yet in a Spec Kit catalogue, so specify asks you to confirm the source. See the README for upgrading.
0.1.3
- Supports Spec Kit 1.x:
speckit_versionis now>=0.12.9.dev0,<1.2.0, tested on 0.12.9 and 1.1.2. - Every command checks all its refusals and reports each one that holds, rather than stopping at the first. A refusal that names a way to continue is followed instead.
cutrefusal 7 allows a gate that grounds its own premise: an[UNGROUNDED]mark settled by the feature's own gate, when the gate states the claim as something it proves.- The README's configuration note covers Spec Kit 1.x, which creates
epic-config.ymlon install. - Shorter manifest description.
Earlier changes are in CHANGELOG.md.
spec-kit-epic 0.1.2
A Spec Kit extension for work too big for one feature: five commands (specify, plan, cut, review, close) that break an epic into features, deliver them in order, and keep the decisions made along the way holding across all of them. Requires Spec Kit 0.12.x and git.
Install
specify extension add --from https://github.com/pmckeown/spec-kit-epic/archive/refs/tags/v0.1.2.zipThe extension is not yet in a Spec Kit catalogue, so specify asks you to confirm the source. See the README for upgrading.
0.1.2
- "What comes next" in
FORMATS.mdno longer namescutfor a feature anopenledger entry touches, whichcutrefuses since 0.1.1. A new row names the owner's decision as the next step. - The README installs from a tagged release and describes upgrading.
0.1.1
cutrefuses a feature while anopenledger entry touches it (refusal 10), unless the owner chooses to cut anyway, recorded in the feature'sstatus_note. Aprovisionalentry is reported, not refused.FORMATS.mddefines anopenentry: options and a recommendation instead of a rejected alternative, answered by a new entry that supersedes it.planrewritesf:<slug>tokens in prose as well as in theFeaturescolumn andtouches:lines, and removes duplicate ids left by merged slugs.specifychecks that every "not yet" Out item has a matchingdeferralentry.
Full history in CHANGELOG.md.