Plan one build, then choose

Use this when the user wants to start a meaningful build and has not already decided how to divide it. The goal is a short, honest plan built from what is actually configured, with the final choice left with the user.

Resolve named models before recommending

A request such as “run subagents through Opus 5.5” already selects a model. Follow the model-request routing in crack; the user need not specify the subscription or adapter. The native planner below does not inventory Claude Code access, so a missing native role is not proof that Opus is unavailable. Check the external adapter separately when requested. Keep route ambiguity, missing access, and unsupported model versions explicit.

Gather local facts only