🎼 Orchestration basics
A minimal orchestrator with three read-mostly helpers (planner, explorer, analyst) that shows how to split analysis and planning across subagents to save context, with stop gates for the user. Start here to learn the pattern; it does not implement code. For a pipeline that also implements, reviews and commits, use plan-explore-review-commit.
Install: orchestration-basics@jaktestowac. See the quick start for each tool.
Start the pack
| Tool | How |
|---|---|
| GitHub Copilot | Pick Orchestrator in the agent dropdown and describe the job. It hands off to the other agents. |
| Claude Code | Run /orchestration-basics followed by the job. The command coordinates; the agents below do the work. |
| OpenAI Codex | Copy codex/agents/ into .codex/agents/, then run $orchestration-basics followed by the job. |
Claude Code and Codex agents cannot start other agents, so there the orchestrator is a command that runs in your conversation.
Agents
| Agent | Name in Claude Code and Codex | What it does |
|---|---|---|
| Orchestrator (orchestrator) | /orchestration-basics command | Coordinates analysis and planning work across the Planner, Explorer and Analyst subagents, synthesizes their findings, and pauses at explicit stop gates for the user. Use for codebase analysis, risk or tech-debt assessment, and phased planning; it does not implement code. |
| Analyst | basics-analyst / basics_analyst | Analyzes code patterns, risks, technical debt and improvement opportunities with file-level evidence, and writes an analysis document. Use when the Orchestrator needs a grounded risk or pattern assessment of part of a codebase. |
| Explorer | basics-explorer / basics_explorer | Maps a codebase read-only and breadth-first (structure, entry points, conventions, usages) and returns file paths with key findings. Use when the Orchestrator needs fast discovery before analysis or planning. |
| Planner | basics-planner / basics_planner | Writes a research-driven, test-first phased plan with risks and success criteria from the findings it is given, and lists any research it still needs. Use when the Orchestrator needs a structured plan before implementation. |
How the pack works, step by step: GUIDE.md.