panel-plan

Fans a written plan out to multiple independent local CLI agents in parallel and synthesizes their findings into one report. Each panelist runs in its own subprocess with no shared conversation state — they see only the plan, the repo it targets (read-only), and the review prompt. That no-shared-state property is the whole point: genuinely independent second opinions on the plan.

This is one review pass, the planning-time sibling of panel-review. It reports; it does not edit the plan. For the iterate → edit → re-review loop that hardens a plan to convergence, use panel-plan-loop, which calls this skill each round.

When to use