CCO | 1 Day
Coordinate fleets of agents instead of doing everything in one conversation. This one-day course shows developers how to break work into sub-agents and orchestrate them: defining agent roles, scoping their tools, and running them in parallel or in pipelines. You’ll build multi-agent workflows hands-on, learning when delegation pays off and when a single session is still the right call. It picks up where the Developer course leaves off.
Who should take this course?
This course is for developers and technical leads who are already comfortable working in Claude Code and want to scale beyond a single session. You should know your way around slash commands, context, and skills, whether from the Developer course or your own use. Comfort with a terminal, a code editor, and your team’s stack is assumed. Come ready to build and run multi-agent workflows throughout the day.
Course Content
This course builds your fluency with multi-agent work, from your first sub-agent to orchestrated pipelines that fan out and reconverge. You’ll work hands-on against real code the way a team would. This is the second of three courses; it builds on Developer and leads into Architect. Each module closes with a hands-on lab.
1. From Solo to Orchestration
- Why one agent isn’t enough: context and focus limits
- The orchestrator and sub-agent model
- When to delegate versus work inline
- Anatomy of a sub-agent: prompt, tools, context
- Reviewing and trusting what comes back
- Hands-on lab
2. Designing Sub-Agents
- Defining agent roles and responsibilities
- Scoping tools and permissions per agent
- Custom agent types and system prompts
- Passing context in, getting results out
- Structured output with schemas
- Hands-on lab
3. Parallel and Sequential Work
- Fan-out: independent agents in parallel
- Pipelines: staged work with dependencies
- Barriers, synchronization, and aggregation
- Avoiding shared-state conflicts with worktrees
- Cost and concurrency trade-offs
- Hands-on lab
4. Orchestration Patterns
- Explore, plan, implement, review workflows
- Adversarial verification and judge panels
- Delegating research and code review
- Keeping the orchestrator in the loop
- When orchestration is the wrong tool
- Hands-on lab