discuss-new-tasklisted

# discuss-new-task Facilitates a short, focused conversation that turns a half-formed issue — the kind that surfaces mid-flight — into a description concrete enough to become a task. This skill is the conversational front-end for `/submit-task`: it clarifies just enough, then proposes the handoff. It never creates or edits any files, including the task list — producing the task(s) is `submit-task`'s job. Most issues are a single task. But some are a bigger chunk of work that only makes sense as **several** tasks — the user may flag this up front ("this might be a few entries"), or it may become apparent mid-discussion that one "issue" is really two or three independent pieces. When that happens, this skill helps draw the boundaries and produces an ordered set of task-sized descriptions, then hands each off in turn. The bar to clear is **conceptual clarity**, not full design detail. For each task that comes out of the discussion, three things must be unambiguous: 1. **Which system** the issue touches (a file, component, section, or requirement). 2. **What the desired behavior is** — what should be true after the fix that isn't true now. 3. **Roughly how you'd verify it** — what you'd look at to confirm it's done. When the work splits into several tasks, one more thing must be clear: **where the boundaries are** — each piece should be independently completable, and their order (what depends on what) should be evident. Once those are clear, `submit-task` takes over — keep