maxlisted

# Maximum Effort Mode The user is requesting comprehensive, parallelized, no-compromise execution. Apply ALL of the following strategies that fit the task. This is not a suggestion list — use every applicable technique. ## Plan First - Decompose the task before executing. For anything with 2+ independent areas, use `/decompose` to produce a reviewable parallel execution plan. - Write atomic, independently-verifiable acceptance criteria up front, then hold the work to them. - If a time budget is given (e.g., `/max 10m`), use it to scope depth and how wide to parallelize. ## Parallelization (Mandatory) Use ALL applicable parallelization patterns: - **Worktree isolation** — For any task touching 2+ independent areas of code, spawn agents with `isolation: "worktree"` so they work on isolated copies. Each agent gets its own branch. Merge results after. See `superpowers:dispatching-parallel-agents`. - **Background agents** — For research, exploration, or investigation that doesn't block other work, use `run_in_background: true`. Don't wait when you don't need to. - **Agent teams** — For 3+ independent workstreams, use `TeamCreate` to coordinate agents with shared task visibility. - **Batch operations** — For similar changes across 3+ files (refactors, renames, migrations), give one agent clear, repeatable instructions over the file list. - **Launch in one message** — All independent research/exploration agents MUST launch in a single message. No staggering