Menü
Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 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 | capture |
| description | Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring. |
Reply rule:
Use $capture when you want to persist an important decision or blocker.
Append a structured entry to:
.codex/anyone-can-code/artifacts/decisions.mdInclude:
This is not a silent prompt monitor. It is an explicit recording step.
When this skill's job is finished: