Menú
After merge, mark a spec completed and archive it per the project convention
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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-close |
| description | After merge, mark a spec completed and archive it per the project convention |
| argument-hint | <spec folder or slug> |
| agent | spec-architect |
Post-merge bookkeeping: mark a shipped spec completed and retire it, so the queue and the docs reflect reality. Runs after the owner accepts and git-merge-pr lands the change. spec-execute-next invokes this in its reset for merged specs; it also runs standalone.
MERGED (gh pr view <pr> --json state,mergedAt) and tasks.md is fully ticked. Not merged or tasks unticked - STOP and report; it is not done.spec-execute Phase D): the feature doc reflects the new behavior, durable rules and decisions were extracted. If anything is missing, apply it now (via spec-document) - the feature doc is the durable record, the spec is not; never close on stale docs.status: completed with the date.specs/_archive/, or delete the plan file if the project deletes shipped plans. Never lose the record silently.status: completed; PR merged and tasks ticked confirmed; the durable feature doc carries the shipped behavior.git-merge-pr (owner accept first). Resuming an unfinished spec - spec-continue.