chainlesschain Orchestrate Workflow
Description
Multi-agent workflow orchestration with predefined templates, agent handoff protocol, and structured inter-agent documents. Inspired by the everything-claude-code orchestrate pattern.
Usage
/orchestrate <template> "description"
Templates
| Template | Agent Chain | Use Case |
|---|---|---|
| feature | planner → architect → coder → reviewer → verification | New feature development |
| bugfix | debugger → coder → tester → verification | Bug diagnosis and fix |
| refactor | architect → coder → reviewer → verification | Code restructuring |
| security-audit | security → coder → security → verification | Security review & fix |
Handoff Protocol
Each agent produces a structured handoff document:
{
"agent": "planner",
"status": "complete",
"deliverables": ["requirements.md", "acceptance-criteria.md"],
"decisions": ["Use Vue 3 composables", "Add Pinia store"],
"concerns": ["Performance impact on large datasets"],
"nextAgentInstructions": "Implement based on requirements..."
}
Output Format
Orchestrate Workflow Report
===========================
Template: feature
Description: "add user profile page"
| Step | Agent | Status | Duration | Summary |
| ---- | --------- | -------- | -------- | -------------------------- |
| 1 | planner | Complete | 5.2s | Requirements defined |
| 2 | architect | Complete | 3.8s | Architecture designed |
| 3 | coder | Complete | 12.1s | Implementation complete |
| 4 | reviewer | Complete | 4.5s | Code review passed |
| 5 | verify | Complete | 28.3s | 6/6 verification passed |
Verdict: SHIP
Total Duration: 53.9s
Verdict Scale
- SHIP - All agents succeeded and verification passed
- NEEDS WORK - Some agents flagged concerns but no blockers
- BLOCKED - Critical failure in one or more agents