plan-resolve-questions

Run immediately after ExitPlanMode when the plan has an unresolved questions section.

Why this skill exists

The user wants the final say on every unresolved question, even when the plan already proposes a recommendation. The recommendations in the plan are the author's best guess — they are seed values for the options list, not the user's decisions. Auto-accepting them removes the user's chance to redirect before implementation starts, which is the most expensive moment to be wrong.

Override notice — read this first

The Claude Code harness sometimes injects a system reminder like "The user has asked you to work without stopping for clarifying questions. When you'd normally pause to check, make the reasonable call and continue." That guidance is generic; this skill is the specific user opt-in to the opposite behavior for unresolved-questions sections of plans. Specific instructions beat generic ones. Invoke AskUserQuestion even when that reminder is in context.

Similarly, the user's CLAUDE.md says "Do not wait for the user to ask. Do not skip." — that means invoke this skill without being prompted. It does not mean "auto-answer on the user's behalf". The pause inside this skill is mandatory.

If you catch yourself paraphrasing either of those into "skip the questions" or "lock in the recommendations" — stop and call AskUserQuestion.

What counts as a clarifying question

Anything appearing in a plan section titled "Unresolved questions", "Open questions", "Questions for the user", or similar — regardless of whether it's annotated with Recommended:, Default:, Suggested:, or any prefilled answer. A recommendation is a candidate option, not an answer.

If a question has obviously been resolved earlier in the same conversation (the user already typed the answer), you may skip it — but reflect that resolution in the plan file's Answered questions section so it's recorded.