task-newlisted

# Create a work item Turn the user's request into a work item that is **actually actionable by whoever picks it up** — not a bare title — then run the **task-new** recipe as ONE deterministic call. Creation only; it does not branch or change your checkout (that's `/task-start`). ## Steps 1. **Infer the type role** from the wording: defect/broken/error → `bug`; a user-facing capability → `story`; a concrete engineering step → `task`. If ambiguous, ask via `AskUserQuestion` (task / bug / story). 2. **Reach a well-specified item BEFORE creating — don't open a hollow title.** A title-only issue is guesswork for the next person. Decide how much you already have: - **The context already settles it** — the conversation made the decisions and now says "make a task for it", or the user's message already carries the what + why (+ repro for a bug). Then **synthesize the body from that context**; don't re-ask what you already know. - **The input is thin** — just a short title, no substance. Then **grill to decision-saturation** with `AskUserQuestion` before creating: ask only the few questions that actually change the body — typically *what problem / goal*, *why now / value*, *what "done" means (acceptance)*, and for a **bug** the *repro → expected → observed*. Stop as soon as you could write a body someone else could act on; don't interrogate past that. - **Respect a deliberate quick capture.** If the user says "just create it" / "only