project-orchestration
Coordinate multiple agents by routing tasks to appropriate specialists. EXCLUSIVE to project-manager agent.
When & Why to Use This Skill
The Project Orchestration skill is a sophisticated multi-agent coordination framework designed for the project-manager agent. It streamlines complex workflows by automatically analyzing user requests and routing them to specialized agents—such as planners, developers, and researchers—using a predefined decision tree and standardized handoff protocols. This ensures seamless task transitions, consistent documentation updates, and optimized resource allocation across the entire development lifecycle.
Use Cases
- Complex Software Development: Coordinating a full-stack feature build by routing UI/UX tasks to designers, database schema changes to DBAs, and logic implementation to developers.
- Automated Bug Resolution: Identifying incoming error reports and automatically dispatching them to the debugger agent followed by a reviewer agent for quality assurance.
- Architectural Planning and Execution: Orchestrating the transition from high-level system design (planner) to technical research (researcher) and final implementation.
- Cross-Functional Project Management: Managing multi-domain requests that require synchronized updates across codebase summaries, standards documentation, and active development branches.
| name | project-orchestration |
|---|---|
| description | Coordinate multiple agents by routing tasks to appropriate specialists. EXCLUSIVE to project-manager agent. |
| allowed-tools | Read, Grep, Glob, Edit, Write |
Project Orchestration
Exclusive to: project-manager agent
Instructions
- Analyze the user request to identify domain(s) involved
- Route to appropriate specialist agent(s) using decision tree
- Use handoff protocol when transitioning between agents
- Update documentation when changes are complete
Agent Roster
| Agent | Domain | Triggers |
|---|---|---|
planner |
Architecture | "plan", "design" |
fullstack-developer |
Implementation | "implement", "build" |
database-admin |
Data layer | "migration", "schema" |
ui-ux-designer |
Interface | "UI", "component" |
researcher |
Research | "research", "compare" |
debugger |
Troubleshooting | "bug", "error", "fix" |
reviewer |
Quality | "review", "check" |
Routing Decision Tree
Request → Is it a bug/error? → debugger
→ Is it a review? → reviewer
→ Is it UI/UX? → ui-ux-designer
→ Is it database? → database-admin
→ Is it research? → researcher
→ Is it planning? → planner
→ Is it implementation? → fullstack-developer
→ Multi-domain? → project-manager
Handoff Protocol
## Handoff: [From] → [To]
- **Completed**: [what was done]
- **Deliverables**: [files]
- **Next**: [what to do]
Task Breakdown Template
| # | Task | Agent | Dependencies |
|---|------|-------|--------------|
| 1 | Design | planner | none |
| 2 | Migration | database-admin | #1 |
| 3 | Implement | fullstack-developer | #2 |
Documentation Sync
| Change Type | Update |
|---|---|
| New feature | docs/codebase-summary.md |
| New model | docs/codebase-summary.md |
| Pattern change | docs/code-standards.md |
Examples
- "Coordinate UI + API + migration work"
- "Break down this feature across agents"