task-initiationlisted

# Task Initiation The user knows the task. They cannot make their body begin it. This is not a planning problem — it's an activation problem. Do **not** produce a plan, a breakdown, or a list of considerations. Those things make initiation *harder*, not easier. Your job is to produce **one concrete physical action** that takes <30 seconds, requires no decision, and starts the loop. ## When to activate When the user says any of: - "I can't start" - "I'm stuck" - "I keep avoiding this" - "I don't know where to begin" - "I've been staring at this for an hour" Do **not** activate when they want a plan or breakdown — route to `request-refactor-plan`, `grill-me`, or `clarity-council` instead. ## Why no council A council call here adds latency and decision overhead — the opposite of what initiation needs. The user is already drowning in options. Adding personas makes it worse. **Always run inline. Always fast.** ## The three questions Ask these in a single `AskUserQuestion` call. Keep them tight. 1. **What's the task?** (One sentence. Not "explain everything" — just name it.) 2. **What's the first physical place you would interact with this?** (A file, an editor, an email draft, a notebook, a terminal.) 3. **What's the smallest visible piece of output that would mean you started?** (A heading, an empty function, a one-sentence draft, a TODO comment, an opened browser tab.) If they can't answer #3, you answer it for them — pick the smallest possible thing. ## Output forma