triage-issuelisted

# Triage Issue Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user. ## Invocation Position This is an invoked helper skill, not a normal first stop for bug work. It normally runs from `/qa` when the per-issue depth check decides a specific reported bug needs root-cause analysis before it can be filed as a lightweight issue. Use `/triage-issue` when the cause is unclear after lightweight exploration, the bug is a regression, reproduction is intermittent, multiple symptoms may share an upstream cause, or the user explicitly asks for diagnosis. Do not use it directly as the entry point for bug conversations — start with `/qa`, which delegates here per issue when depth is warranted. Do not use it once the fix task is already clear enough for `/execute` either. > **One question per turn.** When the diagnosis requires user input, ask one question at a time and wait for the answer before asking the next. Triage is mostly hands-off — minimize questions, but the ones you ask are sequential. > > **Prefer single-select.** Use single-select multiple choice when the user is choosing one direction, one priority, or one next step. > > **Use multi-select rarely.** Reserve it for compatible sets — goals, constraints, non-goals, success criteria — that can all coexist. If prioritization matters, follow up asking which selected item is primary. > > **Use the platform's ques