home / skills / htooayelwinict / claude-config / project-orchestration

project-orchestration skill

safe

This skill orchestrates multi-agent routing by analyzing requests, selecting specialists, and coordinating handoffs to deliver coordinated project outcomes.

npx playbooks add skill htooayelwinict/claude-config --skill project-orchestration

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

2.0 KB

---
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

1. Analyze the user request to identify domain(s) involved
2. Route to appropriate specialist agent(s) using decision tree
3. Use handoff protocol when transitioning between agents
4. 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

```markdown
## Handoff: [From] → [To]
- **Completed**: [what was done]
- **Deliverables**: [files]
- **Next**: [what to do]
```

## Task Breakdown Template

```markdown
| # | 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"

Overview

This skill coordinates multiple specialist agents by routing tasks to the appropriate expert and managing handoffs. It is exclusive to the project-manager agent and ensures work is broken down, delegated, and tracked until documentation is updated. The goal is clear responsibility, fewer context gaps, and predictable deliverables. It streamlines multi-domain requests into actionable agent tasks.

How this skill works

The skill analyzes the incoming request to identify domains and match triggers to the agent roster. It applies a decision tree to route single-domain work directly or retain coordination for multi-domain items. When transferring work, it issues a structured handoff containing completed items, deliverables, and next steps. After tasks finish, it updates the designated documentation files based on change type.

When to use it

Coordinating work across multiple domains (UI, API, DB, etc.).
Breaking a feature request into agent-specific tasks and dependencies.
Routing bug fixes, reviews, or research to the correct specialist.
Creating a clear handoff between designers, devs, and ops.
Ensuring documentation is updated after architecture or pattern changes.

Best practices

Perform an initial domain analysis before assigning tasks to avoid rework.
Use the provided handoff protocol for every agent transition to preserve context.
Define dependencies in a compact task breakdown table to keep order unambiguous.
Prefer one owner for cross-domain coordination: the project-manager agent.
Update the appropriate docs (codebase-summary or code-standards) immediately after changes.

Example use cases

Coordinate a UI redesign that requires new API endpoints and a database migration.
Break down a new feature into design, schema changes, implementation, and QA tasks.
Route an urgent bug to the debugger, then hand off fixes to the developer and reviewer.
Assign research to compare third-party services, then route results to planner for architecture decisions.
Organize a release that needs migration, implementation, and final review steps.

FAQ

Which agent receives a request for multiple concerns?

If the request spans multiple domains, the project-manager agent retains orchestration and creates per-agent tasks rather than routing to a single specialist.

What minimum content should a handoff include?

Every handoff must state what was completed, list deliverables (files or links), and specify the next action and owner.