← ClaudeAtlas

execute-phase-bglisted

Background-dispatch variant of execute-phase. Spawns one `claude --bg --agent maxvision-executor` session per plan (with auto-worktree) instead of running waves of in-process Agent calls. Frees the main session immediately. Use when the phase has multiple independent plans, the work is long-running, and you want to monitor via `claude agents` instead of staying attached.
produtoramaxvision/maxvision · ★ 1 · AI & Automation · score 73
Install: claude install-skill produtoramaxvision/maxvision
# Execute phase in background Argument: `$phase_arg` — phase number (e.g. `3`) plus optional flags: - `--limit=N` — cap the number of background sessions dispatched (default: all incomplete plans, max 10) - `--dry-run` — print the dispatch plan without invoking claude This skill is the **async cousin** of `execute-phase`. It does NOT replace the wave-of-N synchronous executor; it adds an opt-in path for users who prefer Agent View workflow over inline subagent dispatch. ## When to use which | Property | `execute-phase` | `execute-phase-bg` | | --- | --- | --- | | Dispatch model | Synchronous wave-of-N Agent() calls | One `claude --bg` per plan | | Main thread | Blocked until all plans return | Free immediately | | Monitoring | Inline progress | `claude agents` UI | | Worktree | Per maxvision-executor (via `isolation: worktree`) | Auto-isolated by CC for each --bg session | | Token cost | Within parent session quota | Independent session quotas (multiplies) | | Best for | Wave coordination, quick plans (<5 min each) | Long-running plans you'll review later | | Failure recovery | Surfaces in conversation | Surfaces in `claude agents` row | ## Hard rules 1. **Manual confirmation required.** Dispatch plan must be approved with `sim`. 2. **Cap at 10 parallel sessions** by default. Each session has independent token quota — fanning out to 30 plans will burn through subscription limits quickly. Override with `--limit=N` and an explicit `--accept-cost` flag. 3. **Refuse on dirt