subagents

Spawn one child per review concern using sub spawn with a self-contained prompt file, then call sub wait with all names and read each result via sub out. Pass --tools read,grep,find,ls to keep reviewers read-only.

Use sub spawn with a name, working directory, and a self-contained task prompt describing the goal, file paths, and expected output. The child runs detached in tmux with fresh context and writes its result to an out file.

Use the cheapest model that fits the role: a lightweight model for recon and summaries, a stronger one for implementation, a high-quality model for review and planning, and a web-capable model for research or ops work. Pass the choice via --model.

Extensions are off by default in headless children. Research children need web tools enabled explicitly by passing --ext with the path to the web access extension when spawning.

Resume only for tightly related corrections where the child's prior file map and decisions materially help. Prefer a fresh spawn with a checkpoint prompt when crossing topic boundaries or after three to four corrective turns.

Two children editing the same worktree concurrently can conflict and corrupt each other's changes. Parallelize read-only work like reviews and recon, but keep only one writer child active at a time.