Menü
Use when a written plan needs coordinated inline execution.
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
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.
Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.
Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.
Consult before implementing an observable behavior change when a meaningful automated test seam exists; use proportional red-green evidence.
Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution.
Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.
| name | executing-plans |
| description | Use when a written plan needs coordinated inline execution. |
Read the plan, stable references, repository state, and progress evidence before acting. Execute by meaningful semantic deliverables, not a fixed task size or a ritual todo list.
Confirm the plan still fits current code, constraints, and user intent. Adapt stale steps when evidence changes the safe path and record why. Stop only for a load-bearing blocker or authority ambiguity: a missing decision that changes safety, architecture, external state, or acceptance.
For each deliverable, establish dependencies, make the bounded change, and gather semantic evidence. Use a worker, worktree, review, or finishing workflow only when it materially improves this deliverable under current harness and repository policy. Do not assume an announcement, commit, or main-branch rule is required.
At closeout report capability, relationships, evidence, and remaining risk. Route a real branch, integration, or discard decision through the applicable authorized repository workflow.
