What problem does it solve? Ambiguous user requests lead to plans built on unstated assumptions or endless clarifying questions. This Skill structures how an architect agent inventories uncertainties, resolves what it can, and escalates only genuine user decisions. ## 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, consults a critic sounding board, then surfaces a structured decision packet. - Critic Verdict Mapping: Maps SoundingBoardVerdict outcomes (UNNECESSARY, RESOLVE, REPHRASE, APPROVED) to funnel actions with hard protections against dropping always-surface categories like scope, data loss, security, and breaking changes. - Assumption Recording and Timeout Handling: Records every resolved uncertainty as an explicit assumption and reclassifies stalled research items to user_decision after a configurable timeout. - Use Case: When asked to plan a feature with unclear migration and rollout implications, the architect runs this funnel to resolve defaults from context, consult the critic, and present only the decisions that genuinely require the user. ## Quick Start Ask the architect agent to plan an ambiguous feature request and it will load this protocol to run the clarification funnel before presenting any questions.
