Orchestration protocols for /workflow pipeline. Load at /workflow startup (step 0.1), then load individual protocols on-demand per event triggers. Covers: handoff contracts (4 phase-to-phase contracts + narrative casting), checkpoint format (session recovery), re-routing (complexity mismatch), pipeline metrics (completion tracking).
| Protocol | When to Load | Purpose |
|---|---|---|
| Handoff | BEFORE forming handoff between phases | 4 pipeline contracts + 1 tool contract (code-researcher) + narrative casting |
| Checkpoint | AFTER completing each phase | Format (12 YAML fields), recovery (5 steps), state persistence |
| State Layer | On-demand (debugging state issues, Phase 5 cleanup) | File contracts, lifecycle rules, cleanup protocol for .claude/workflow-state/ |
| Re-routing | On complexity mismatch signal | Downgrade/upgrade route + tracking + learning |
| Pipeline Metrics | At completion phase only | Format (12 fields), storage (JSONL file), analysis, anomaly detection |
| Agent Memory | Agent startup + completion | Shared memory behavior for all memory: project agents |
| Parallel Dispatch | 2+ independent tasks identified (L/XL) |
| Multi-agent dispatch patterns (research + future debugging) |
Read this SKILL.md for protocol overview. Then load Core Deps files: Autonomy, Orchestration Core.
Do NOT load all protocols upfront. Load on-demand per Event Triggers below:
CRITICAL: Every phase MUST produce a structured handoff payload (context + artifact + metadata) for the next phase. Read Handoff Protocol for the 4 pipeline contracts (+ 1 tool contract for code-researcher) before forming any handoff.
Good — full handoff payload (planner → plan-review):