|
| 1 | +--- |
| 2 | +name: task-orchestrator |
| 3 | +description: Coordinate multi-agent software execution with Task Orchestrator using commander intent, dependency chains, and live status commands. Use when an agent must break down work, assign tasks, track progress, or unblock dependent work with tm. |
| 4 | +license: MIT |
| 5 | +compatibility: Designed for filesystem-based coding agents (Codex, Claude Code, similar tools). Requires shell access, Python 3.8+, and executable tm in the project root. |
| 6 | +metadata: |
| 7 | + author: T72 |
| 8 | + version: "1.0" |
| 9 | +--- |
| 10 | + |
| 11 | +# task-orchestrator skill |
| 12 | + |
| 13 | +Use this skill when the user needs reliable agent coordination with `tm`. |
| 14 | + |
| 15 | +## Activation cues |
| 16 | + |
| 17 | +Activate this skill when requests involve: |
| 18 | + |
| 19 | +- delegating to multiple agents |
| 20 | +- sequencing dependent tasks |
| 21 | +- sharing context between assignees |
| 22 | +- tracking progress or blocked work |
| 23 | +- orchestrating a delivery pipeline |
| 24 | + |
| 25 | +## Prerequisites |
| 26 | + |
| 27 | +1. `tm` exists in the current project root. |
| 28 | +2. The project has been initialized with `./tm init`. |
| 29 | +3. `TM_AGENT_ID` is set for the current agent session. |
| 30 | + |
| 31 | +## Startup protocol (always) |
| 32 | + |
| 33 | +```bash |
| 34 | +./tm list |
| 35 | +./tm list --format json |
| 36 | +``` |
| 37 | + |
| 38 | +Do not treat `ORCHESTRATOR.md` as live runtime state. It is a static discovery contract. |
| 39 | + |
| 40 | +## Standard workflow |
| 41 | + |
| 42 | +1. Set identity: |
| 43 | + ```bash |
| 44 | + export TM_AGENT_ID="orchestrator_agent" |
| 45 | + ``` |
| 46 | +2. Create tasks with Commander's Intent: |
| 47 | + ```bash |
| 48 | + ./tm add "Implement auth API" --assignee backend_agent \ |
| 49 | + -d "WHY: secure user access, WHAT: login/token/session endpoints, DONE: users can authenticate successfully" |
| 50 | + ``` |
| 51 | +3. Add dependencies: |
| 52 | + ```bash |
| 53 | + ./tm add "Create login UI" --assignee frontend_agent --depends-on <backend_task_id> |
| 54 | + ``` |
| 55 | +4. Share handoff context: |
| 56 | + ```bash |
| 57 | + ./tm share <task_id> "API contract: POST /auth/login, POST /auth/refresh" |
| 58 | + ``` |
| 59 | +5. Track progress: |
| 60 | + ```bash |
| 61 | + ./tm progress <task_id> "Implemented token issuance and refresh validation" |
| 62 | + ``` |
| 63 | +6. Complete to trigger unblocking: |
| 64 | + ```bash |
| 65 | + ./tm complete <task_id> |
| 66 | + ``` |
| 67 | + |
| 68 | +## Coordination rules |
| 69 | + |
| 70 | +- Query state with `./tm list` before creating or updating tasks. |
| 71 | +- Include `WHY`, `WHAT`, and `DONE` in all substantive delegated tasks. |
| 72 | +- Use `./tm share` for cross-agent information, not private notes. |
| 73 | +- Use `./tm note` only for private reasoning. |
| 74 | +- Keep commands non-interactive and deterministic. |
| 75 | + |
| 76 | +## Safety and quality |
| 77 | + |
| 78 | +- Avoid destructive operations unless explicitly requested. |
| 79 | +- If task state conflicts with assumptions, re-query `./tm list --format json`. |
| 80 | +- For release-related orchestration, run from release source branch policy (`main` unless overridden by process). |
| 81 | + |
| 82 | +## Available resources |
| 83 | + |
| 84 | +- Runtime checks: `scripts/verify-tm.sh` |
| 85 | +- Extended reference: `references/REFERENCE.md` |
| 86 | + |
0 commit comments