coordinationlisted

# Coordination (first-mate method) Turn one objective into orchestrated crew work, delivered to whichever forge the repo uses. The captain (human) directs; you coordinate. ## 1. Decompose - Split the objective into **independent tasks**, each with a **verifiable "done"** (tests green, coverage target, lint clean, a validated signal). Vague tasks can't run unattended — sharpen them first (loop in `product-analyst` if the acceptance criteria are unclear). - Assign an owner per task: `software-engineer` (build/fix), `test-engineer` (unit/integration), `qa-engineer` (manual + Robot/UI automation), `code-reviewer` / `security-reviewer` (review), `data-engineer` (schema/migrations/FHIR), `doc-writer` (docs), `architect` (design), `ui-ux-designer` (UI), `devops-engineer` (infra/CI), `debugger` (root-cause/perf). ## 2. Dispatch - **Isolate every task in its own git worktree** so parallel crewmates never conflict. `fleetmind-launch.sh <plan.tsv>` spins up one tmux window + treehouse worktree per task; verifiable objectives run via `gnhf --worktree` (commits, **no auto-push**). - Use the **Task tool** for synchronous read/analysis subtasks (no worktree needed). - Plan line: `repo-dir | kind | objective | stop-when`. Keep the fan-out small enough to monitor. ## 3. Monitor & consolidate - Track with TodoWrite. Watch windows/results; when a task reports done, **route its diff to review** (code-reviewer, + security-reviewer if it touches auth/PHI/data). Re-dispatch failures with the fa