skills/ce-plan/references/bakeoff.md

# Bake-off in planning

Use `ce-bakeoff` only when explicitly requested, on a Standard/Deep Durable plan with a consequential unresolved HOW whose alternatives need development. Preserve the existing output/depth reclassification rules. A settled product direction does not settle unspecified technical choices, but a specifically settled HOW cannot be reopened merely to run a competition. If no eligible decision remains, state why and continue normal planning.

After research and before fixing that decision or dependent units, resolve model preferences using the activation-resolution rules in `references/reasoning-elevation.md`. Pass the resolved preference, including explicit restrictions, to `ce-bakeoff` with the requirements, question, full research evidence, settled decisions, project constraints, budget, and approach-sketch fidelity. An explicit candidate model mix takes precedence. Bake-off owns fresh candidate dispatch and fallback; do not run the plan-authoring adapter for each baker. With no preference, allow Bake-off's default model-family exploration.

Bake-off owns exploration through selection. Carry its complete return into the technical-decision rationale and dependent units without changing stable identifiers or inventing user approval. Preserve incomplete/unresolved status: if it prevents a defensible plan, use planning's existing blocker contract; otherwise disclose the missing comparison and continue on the available evidence.

The existing final interpret-and-author elevation still runs at its normal boundary. Give that author the complete Bake-off result and sources. It incorporates the selected approach and surfaces material contradictory evidence instead of silently rerunning the competition. Normal confidence, review, and handoff rules remain authoritative.