菜单
Use when coordinating multi-step work across workers or subagents, especially when research, implementation, and verification should be split while the main agent stays responsible for synthesis and user communication
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when verifying implementation work and the failure mode is superficial approval, code-reading in place of execution, or over-trusting a passing test suite without trying to break the change
Use when the task is codebase exploration rather than modification, and you need a fast, read-only search pattern that starts broad when location is unknown, narrows when location is known, and parallelizes independent searches
Use when deciding what information belongs in memory, how to classify it, and what must not be saved because it is derivable from the repo, git history, or current task context
Use when deciding whether shell commands are truly read-only, safe for concurrent execution, and free of path, git, redirection, or command-shape risks that should force a stricter permission path
Use when the real risk is not lack of knowledge but self-justifying shortcuts such as explaining instead of running commands, skipping the hard part first, or deciding on your own that verification would take too long
Use when maintaining session notes that must preserve a fixed markdown template, stay within section and total token budgets, and remain useful after compaction or resume
| name | coordinator-orchestrator |
| description | Use when coordinating multi-step work across workers or subagents, especially when research, implementation, and verification should be split while the main agent stays responsible for synthesis and user communication |
Act as the coordinator, not the extra pair of hands. Launch workers for research, implementation, and verification, but keep planning, synthesis, and user-facing judgment on the main thread.
This pattern is grounded in src/coordinator/coordinatorMode.ts: the coordinator owns decomposition, prompt quality, result synthesis, and communication.
Your main job is to understand worker output before issuing follow-up work.
Never write prompts like:
Write prompts like:
src/auth/validate.ts:42."src/foo.ts and src/foo.test.ts to preserve the old error contract."If you cannot explain the change precisely, you have not finished the synthesis step.
Continue the same worker when:
Spawn a fresh worker when:
Before sending work to a worker, include:
You have applied this skill correctly when the coordinator remains the decision-maker, workers receive self-contained tasks, and every follow-up prompt proves that you understood the previous results.