start-discussion - explore before committing to a track

Not every conversation arrives with a known piece of work. Sometimes the user has a problem they don't yet know how to frame, or an idea they want to think out loud. /start-discussion holds that space.

It does not write files. It does not commit to a track. It draws out context until the work itself becomes clear - at which point it hands off to /start-feature (or directly to /plan-change if the next move is obvious).

What this skill does

1. Reflects what the user said back, so they know you heard them.
2. Asks open-ended questions that pull out context, constraints, and what "good" would look like.
3. As intent crystallises, names what's emerging and offers to route into the right next skill.