What problem does it solve? Ambiguous user requests lead to plans built on unstated assumptions or excessive clarifying questions. This protocol inventories every material uncertainty, resolves what it can from context and a critic sounding board, and surfaces only genuine user decisions as a structured packet. ## Core Features & Use Cases - Four-Stage Clarification Funnel: Inventories all material uncertainties, classifies each as self_resolved, critic_resolved, research_needed, user_decision, or deferred_nonblocking, then consults a critic sounding board before asking the user anything. - Always-Surface Protection: Categories like scope boundaries, destructive behavior, security risk, and breaking changes must reach the user; DROP verdicts on these items are overridden to ASK_USER. - Assumption Recording: Every resolved uncertainty is recorded as an explicit assumption in the spec, plan, or context file, preventing silently dropped decisions. - Use Case: When asked to plan a feature with unclear migration and rollout implications, the architect runs this funnel to resolve defaults internally and presents only the blocking scope and compatibility decisions to the user. ## Quick Start Activate MODE: CLARIFY on an ambiguous request to run the clarification funnel and produce a structured user decision packet.
