Orchestrate

Invoked as /agiflow:orchestrate. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.

Usage:

• /agiflow:orchestrate - Check pipeline state and dispatch the next highest-priority task

---

Guardrails

• This is a read-assess-dispatch loop, not an implementation prompt.
• Do NOT implement tasks here, use /agiflow:run-task for that.
• Keep capacity checks honest: do not dispatch if at capacity.
• Report pipeline state even when no dispatch is needed.

---

AgiFlow Project Management Guidelines

Follow the shared AgiFlow project-management guidelines in references/agiflow-agents.md, agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.

---

Steps Track these steps as TODOs and complete them one by one.

1. Assess Current Pipeline State

1. Use list_tasks to count tasks in each active status column:

   • status: "In Progress", tasks currently being coded by agents
   • status: "Testing", tasks running test suites
   • status: "Review", tasks awaiting human review
   • status: "Blocked", tasks requiring human intervention
   • status: "Todo", tasks ready for pickup (sorted by priority automatically)

2. Report the pipeline state in a concise table:

   Pipeline State:
   ┌──────────────┬───────┐
   │ Status       │ Count │
   ├──────────────┼───────┤
   │ Todo         │   N   │
   │ In Progress  │   N   │
   │ Testing      │   N   │
   │ Review       │   N   │
   │ Blocked      │   N   │
   └──────────────┴───────┘
   

2. Check Capacity