メニュー
Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement commands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | skill-orchestrator |
| description | Route commands to appropriate workflows based on task type and status. Invoke when executing /task, /research, /plan, /implement commands. |
| allowed-tools | Read, Glob, Grep, Agent |
Central routing intelligence for the task management system.
Load context on-demand when needed:
@.claude/context/orchestration/orchestration-core.md - Routing, delegation, session tracking@.claude/context/orchestration/state-management.md - Task lookup and status validation@.claude/context/index.json - Full context discovery indexThis skill activates when:
Given a task number, retrieve full context:
1. Read specs/state.json
2. Find task by project_number
3. Extract: task_type, status, project_name, description, priority
4. Read TODO.md for additional context if needed
Route to appropriate skill based on task type:
| Task Type | Research Skill | Implementation Skill |
|---|---|---|
| general | skill-researcher | skill-implementer |
| meta | skill-researcher | skill-implementer |
| markdown | skill-researcher | skill-implementer |
Note: Additional languages (latex, typst) are available via extensions in .claude/extensions/.
Before routing, validate task status is not terminal:
if status in [completed, abandoned, expanded]:
ABORT "Task is in terminal state [$status]"
All operations (research, plan, implement, revise) are allowed from any non-terminal status.
Prepare context package for delegated skill:
{
"task_number": 259,
"task_name": "task_slug",
"task_type": "general",
"status": "planned",
"description": "Full task description",
"artifacts": {
"research": ["path/to/research.md"],
"plan": "path/to/plan.md"
},
"focus_prompt": "Optional user-provided focus"
}
1. Receive command context (task number, operation type)
2. Lookup task in state.json
3. Validate status for operation
4. Determine target skill by task_type
5. Prepare context package
6. Invoke target skill via Agent tool
7. Receive and validate result
8. Return result to caller
{
"status": "completed|partial|failed",
"routed_to": "skill-name",
"task_number": 259,
"result": {
"artifacts": [],
"summary": "..."
}
}
After routing to a skill, this skill MUST NOT:
The orchestrator is a routing-only skill. It:
Reference: @.claude/context/standards/postflight-tool-restrictions.md
Orchestrate multi-agent implementation with parallel phase execution. Spawns teammates for independent phases and coordinates dependent phases. Includes debugger teammate for error recovery.
Orchestrate multi-agent planning with parallel plan generation. Spawns 2-3 teammates for diverse planning approaches and synthesizes into final plan with trade-off analysis.
Orchestrate multi-agent research with wave-based parallel execution. Spawns 2-4 teammates for diverse investigation angles and synthesizes findings.
Full structural hard-mode orchestration state machine with per-phase dispatch (H1), adversarial verification (H4), convergence policing (H6), territory contracts (H7), and churn detection (H5). Invoke for /orchestrate --hard.
Autonomous state machine that drives a task through its full lifecycle (research -> plan -> implement -> complete) without user confirmation between phases. Invoke for /orchestrate command.
Execute hard-mode implementation with anti-analysis contracts, per-phase dispatch, and territory-aware execution. Invoke for --hard implementation tasks.