executing-plans
星标1
分支1
更新时间2026年7月12日 06:40
Use when a written plan needs coordinated inline execution.
安装
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
SKILL.md
readonly
下载
相关职业SOC
基于 SOC 职业分类
菜单
Use when a written plan needs coordinated inline execution.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.