Menu
Use when a change would alter accepted scope/plan and needs user confirm. Not for tiny in-scope edits.
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
Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify.
Use when goal/spec is clear and you need ordered tasks before writing code. Not while still clarifying.
Use when about to claim done/works/fixed, or user asks test/check/prove. Run evidence; not for pure planning chat.
Use when another installed plugin/skill may do the job better, or to route specialists. ACC stays workflow owner.
Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring.
Use when request is too vague to plan or build. Not when goal and constraints are already clear.
| name | govern |
| description | Use when a change would alter accepted scope/plan and needs user confirm. Not for tiny in-scope edits. |
Reply rule:
Use $govern when a proposed change could materially alter the accepted scope.
.codex/anyone-can-code/state/workflow.json.codex/anyone-can-code/artifacts/SPEC-DRAFT.md.codex/anyone-can-code/artifacts/PLAN.md.codex/anyone-can-code/state/task-queue.mdscripts/canonical_state.py; plans and task queues are
derived views, not separate truth.Approved scope change that rewrites large parts: suggest Worktree mode — a safe copy, real project untouched until the change proves itself.
When this skill's job is finished: