always-ask-on-unresolved
Always Ask on Any Unresolved Item — Mandatory AskUserQuestion Usage
Section titled “Always Ask on Any Unresolved Item — Mandatory AskUserQuestion Usage”You MUST invoke AskUserQuestion for ANY unresolved item. Prose “A or B?”, choice lists and “Pick one of:” blocks are violations. The seven triggers: (1) a prose question you would put to the user, unless the answer is on record; (2) an unresolved plan item before proceeding (TBD, TODO, ??, phase conflict); (3) an unresolved report item before it is final; (4) an ambiguity found mid-implementation the plan does not cover; (5) a default or policy choice not handed to you (thresholds, fallbacks, retention); (6) a deletion, overwrite or destructive action with non-trivial blast radius; (7) a skill needing a multi-option decision.
When in doubt, ask. A closing offer or rhetorical question in a finished turn is no unresolved item when the marker gives reason=; destructive, credential and consent asks still use AskUserQuestion. Out-of-scope findings are not unresolved items: park them (off-scope-finding-offload.md). Plan/report deliverables: batch unresolved markers into AskUserQuestion. If AskUserQuestion is deferred: load the schema and call it — deferral is NEVER a justification for a prose fallback.
Narrow exceptions (when NOT to ask)
Section titled “Narrow exceptions (when NOT to ask)”Table, protocol, deferred-tool recipe: docs/always-ask-on-unresolved.md · docs/decision-discipline-examples.md § “the tool is deferred”.