Decision framework for what to cut when a spec, sprint, or launch is too big for the time or team available. Use whenever a PM says a scope needs to shrink, a deadline is fixed and the work isn't, or someone asks "what can we cut" or "what's the MVP version of this." Also trigger when reviewing a spec that feels bloated before it goes to engineering. Distinct from prioritization frameworks (RICE, MoSCoW): this is specifically about which cut preserves the point of the release versus which cut guts it while looking similar on paper.
