Parallel plan drafting with worktrees Use this when multiple new follow-up issues need canonical plan drafts at the same time, but implementation is blocked by the planning gate. Typical trigger: - a parent execution wave reveals multiple new follow-up issues - each follow-up needs a plan, not code - you want parallel progress without colliding in or other shared planning files Why this pattern exists A safe parallel planning wave needs four things together: 1. isolated worktrees per issue 2. explicit planning-only prompts 3. backgroundable Codex runs with durable logs 4. centralized handoff/…