ask-user-questionslisted

# Ask User Questions — Structured QCM Workflow ## Why this exists When you (the agent) need clarifications, asking inline in chat is unreliable: long responses get skimmed, formats vary, and answers are lost in the conversation. Instead, you write a structured QCM markdown file grouped by theme. The user reviews it in their editor, marks their choices, optionally adds notes, saves. You re-read the file and continue. This is more stable, traceable (the files live in `.questions/`, gitignored), and lets the user answer at their own pace without breaking flow. It also works well for batch-asking (e.g., a triage at the start of a phase). ## When to use this skill **Use it when:** - You face an ambiguity that materially affects the result (architecture choice, naming convention, library selection, scope boundary). - You need a preference (style, tradeoff, priority) that you cannot infer from existing context. - You're triaging a phase or sprint and have several decisions to surface at once. - You'd otherwise have to guess and risk wasted work. **Do NOT use it when:** - The answer is already in `CONTEXT.md`, the codebase, or the recent conversation. Re-read first. - It's a trivial yes/no the user just answered moments ago. - The task is purely mechanical and unambiguous. If in doubt, prefer asking via this skill over guessing silently. ## Setup (first time in a project) If `.questions/` does not exist at the project root: 1. Create the directory: `.questions/`. 2. Create