Menu
Mark a reviewed spec approved so it enters the autonomous execution queue
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.
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
Based on SOC occupation classification
| name | spec-approve |
| description | Mark a reviewed spec approved so it enters the autonomous execution queue |
| argument-hint | <spec folder or slug> |
| agent | spec-architect |
The owner's gate-1 decision, recorded as a machine-readable signal: an approved spec is what spec-execute-next picks up. This decouples review from execution - approve a batch of specs now, and the AI works the approved queue later (scheduled or looped), with no further owner input until the PR.
proposed spec). Read requirements, plan, and tasks end-to-end.proposed (not already approved / in-progress / completed / cancelled); the plan cites concrete siblings; no open question is left that would block a cold executor. Surface anything that should block approval - the owner decides, this skill only records the decision.status: approved with the date. Change nothing else - approval records a decision, it does not edit spec content.spec-execute-next will pick it up by value, or run spec-execute to start it now.status reads approved; nothing else in the spec changed.spec-create (update-mode). Executing - spec-execute / spec-execute-next.approved on its own initiative (not inside spec-create, not autonomously) - only when the owner explicitly invokes this skill after reviewing.proposed spec; re-approving or approving a mid-flight spec is a no-op with a warning.