rafmacalaba/armada/armada-dispatch

Armada: Parallel Subagent Dispatch

When two or more tasks are independent, dispatch them as parallel subagents. The key constraint: parallel tasks must write disjoint files. Shared files force serialization.

Rules

1. Build a dependency graph from the phase list. Independent phases (no shared deps) can run in parallel.
2. Check file scope: two phases can run in parallel only if they never write the same file. Prefer per-phase file isolation (e.g. src/<feature>.js + its test).
3. Backend-dev and frontend-dev within the same phase can run in parallel when the API contract is fixed first, since they write different source trees.
4. Wait for all dispatched subagents to return before gating the phase. Do not end your turn with background work outstanding.
5. When NOT to parallelize: shared output file, sequential dependency between tasks, or one task's output is the other's input. Serialize writers on a reused subagent session.

Example: Phase 2 (API) and Phase 3 (UI) are independent and write src/api/ vs src/ui/ — dispatch both as parallel background subagents.

Adaptive roster

• Infer risk from changed surface; keep non-required roles standby.
• QA is always active. Low risk uses implementer + QA; high risk adds security and adversary, with

architect for shared or cross-cutting design.

• Separate voyages use separate worktrees and run concurrently. Return compact receipts with

Status, Files, Evidence, Result, Risks, and Next.