issue-triagelisted

# Issue Triage Read-only triage of a bug or defect. Gathers context, maps the suspected code area, hypothesizes root causes, and produces a ranked triage report with proposed investigation paths. **Read-only by default.** The skill never modifies Confluence pages, MRs, or code files, and never changes Jira ticket fields. The single exception is Phase 7: with explicit user opt-in, the final report may be posted as a comment on the originating Jira ticket. ## Input One of: 1. **Jira ticket key** — pattern `[A-Z][A-Z0-9]+-\d+` (e.g. `PROJ-1234`) 2. **Free-form description** — a narrative description of the issue, error message, or symptom If neither is clear from the user's message, ask which they want to triage. ## Workflow ```text Triage Progress: - [ ] Phase 1: Gather issue context - [ ] Phase 2: Map suspected code area (codebase-explain) - [ ] Phase 3: Pull related signals (git, MRs, sibling tickets) - [ ] Phase 4: Clarify gaps with the user (grill-me) - [ ] Phase 5: Hypothesize root causes (clarity-council) - [ ] Phase 6: Produce triage report - [ ] Phase 7: Optionally publish report as Jira comment (user opt-in) ``` ### Phase 1 — Gather issue context **If Jira ticket:** - `jira_get_issue` — summary, description, type, priority, status, components, labels, affected version, environment. - `jira_get_comments` — capture user-reported reproduction steps and prior investigation notes. - `jira_get_changelog` — note recent status changes, reassignments, or version field