Menu
Cancel or supersede a spec, recording the reason so the decision is preserved
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Verify, review, and push pending work as one milestone commit
Drive the current branch's PR to merge-ready: CI green and every review comment handled, ending with an outcome label
After owner accept: guard-checked squash-merge of the current branch's PR, base sync and branch cleanup
Open a pull request for the current branch against its target, using the repo template
Triage PR review comments: fix, discuss, or decline with reason - every thread answered
Cut a release: version, changelog, tag, and release object — policy-driven across trunk/gitflow and tag-only/full
| name | spec-cancel |
| description | Cancel or supersede a spec, recording the reason so the decision is preserved |
| argument-hint | <spec folder or slug> [superseded-by <NNN>] |
| agent | spec-architect |
Retire a spec that will not ship - the owner dropped it, scope changed, or another spec replaces it - without losing why. A cancelled spec is a recorded decision, not a deleted file.
cancelled (will not be done) or superseded by NNN (another spec replaces it). The reason is required.status: cancelled (or status: superseded by NNN, with both linked) plus a one-line reason and the date in the spec's front page.spec-document): a stubbed feature doc or an inferred rule that describes behavior which never shipped is removed or clearly marked not-shipped - never leave orphan docs implying a change that did not land.status reads cancelled or superseded; the reason is recorded; a supersede chain links both ways; no pushed work was deleted.spec-create (the superseder); link it. A reversible decision worth a durable record beyond the spec - spec-decision.