Claude for ambiguity
Product calls, architecture, confusing requirements, and the hardest review pass.
Models, coding surfaces, agent skills, and MCP servers ranked for Waterfall fit, not universal supremacy. Every pick says what it is for, why it earned a place, and when to leave it off.
Do not burn one plan to zero and then drag a cold project into the other. Give each agent a distinct job and preserve a compact shared handoff.
Product calls, architecture, confusing requirements, and the hardest review pass.
Repository work, parallel agents, worktrees, tests, and autonomous execution.
One agent owns the change. The other gets a narrow review brief and no incentive to defend it.
A popular tool can still lose if it creates more context, permission, billing, or maintenance cost than useful work. skills.sh installs and mcp.directory discovery are signals, not quality or security verdicts.
A named recurring job, not a generic promise to make agents better.
Official sources, dated benchmarks, or observed local use.
An honest reason to keep it off or choose something else.
No copied secrets, machine config, or unlicensed third-party code.