Menu
Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify.
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 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.
Use when verify failed, same error twice, or something is broken. Diagnose before retry; not for first green build.
| name | execute |
| description | Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify. |
Reply rule:
Use $execute when the work is planned or concrete enough to implement.
Do not say "done", "works", "fixed", or "perfect" in this skill.
After meaningful progress → $verify. Built here = implemented only, never
verified.
Do not invent new product scope. Follow plan / task queue. Scope change → update route first, then continue.
| Thought | Reality |
|---|---|
| "Looks done" | Run $verify. No proof → not done. |
| "Tests can wait" | Verify owns proof. Hand off. |
| "Small extra feature" | Scope creep. Plan or ask. |
| "Should pass" | Not evidence. $verify. |
.codex/anyone-can-code/artifacts/PLAN.md.codex/anyone-can-code/state/task-queue.mdtool_interop execute bindings: use installed skill; ACC redirect only; PRECHECK fail → local ACC + reason.
scripts/canonical_state.py and claim tasks through
scripts/task_coordination.py before execution.scripts/safety_receipts.py first.patch_retry present and a failed patch occurs: reread exact target before retry.mechanics_docs_gate marks platform mechanics work, do not edit code
until the docs brief exists (platform mechanics).references/execute-details.md.scripts/walkaway_pack.py --goal, then native /goal..codex/anyone-can-code/artifacts/Big refactor: tell user Worktree mode (safe copy; Handoff merges). Git only; no Git → local with care.
Next: $verify before any done claim. On fail → $fix.
When this skill's job is finished: