multi-worklisted

# Multi-Work ## Strategy Selection - Task decomposes into independent parallel units → **DAG** (Strategy 1) - Same conclusion needs multi-perspective challenge → **Critique-Chain** (Strategy 2) - Strategies can be nested: any node in either strategy can spawn its own sub-strategy. ## Handoff File Convention (applies to both strategies) All sub-agent outputs must be written to `docs/multi-work/{topic}/{YYYYMMDD}-{short-description}-{Agent-type}{id}.md`. - **Location**: `docs/multi-work/{topic}/` - **Naming**: `{YYYYMMDD}-{short-description}-{Agent-type}{A/B/C/...}.md` (e.g. `docs/multi-work/auth-refactor/20260517-initial-proposal-ExplorationA.md`) - **Format**: Markdown, self-contained — the file alone must be intelligible to a reader who has no other context. - **Audience**: write every handoff file as if it will be reviewed by the highest authority (Linus). Be thorough, be honest about uncertainty, and do not bury tradeoffs. Main Agent passes only the file reference to the next agent. Never paraphrase or summarize handoff content — the next agent reads the file directly. ### Quality Gate (self-check before handoff) Each agent must verify before writing the handoff file: - [ ] File is self-contained — intelligible with zero external context - [ ] Tradeoffs and uncertainties are explicit, not buried - [ ] Acceptance criteria from the spawn prompt are addressed - [ ] No implementation details leaked from outside the assigned scope - [ ] Written for human review — hones