comPACT

Dispatch concurrent specialists for this self-contained task: $ARGUMENTS

MANDATORY: invoke concurrently for independent sub-tasks. Sequential requires explicit file conflict or data dependency. If the task contains multiple independent items (bugs, endpoints, components), dispatch multiple specialists together — same type or mixed types — unless they share files.

⚠️ Independent ≠ same domain. "Fix CSS layout + add server logging" = 1 frontend-coder + 1 backend-coder in parallel. The key criterion is independence (no shared files, no data dependencies), not domain uniformity.

---

Task Hierarchy

Create a simpler Task hierarchy than full orchestrate:

1. `TaskCreate`: Feature task "{verb} {feature}" (self-contained task) — stamp metadata.variety.total (see below)
2. `TaskUpdate`: Feature task status = "in_progress"
3. Analyze: How many agents needed?
4. `TaskCreate`: Agent task(s) — direct children of feature
5. `TaskUpdate`: Agent tasks status = "in_progress"
6. `TaskUpdate`: Feature task addBlockedBy = [all agent IDs]
7. Dispatch agents concurrently with task IDs
8. Monitor via `TaskList` until all agents complete
9. `TaskUpdate`: Agent tasks status = "completed" (as each completes)
10. `TaskUpdate`: Feature task status = "completed"

Steps 8-10 are detailed in the After Specialist Completes section below (includes test verification and commit steps).

Feature-task variety stamp (step 1). Stamp the feature-level variety total on the feature TaskCreate, so the wrap-up Orchestration Retrospective can compute feature-vs-dispatch divergence instead of feature_variety_missing:

`TaskCreate(subject="{verb} {feature}", metadata={"variety": {"total": N}})`  # N = feature-level total, 4-16

Advisory, not enforced — the feature task has no teachback-gated sibling, so the dispatch-boundary gate cannot apply. The .total field is the load-bearing input compute_variety_divergence reads (the full D11 4-rationale block is fine too, but .total is the minimum). Mirrors what orchestrate.md already persists for its feature task.

Example structure:

[Feature] "Fix 3 backend bugs"           (blockedBy: agent1, agent2, agent3)
├── [Agent] "backend-coder: fix bug A"
├── [Agent] "backend-coder: fix bug B"
└── [Agent] "backend-coder: fix bug C"

---