bug-triagelisted

Bug diagnostic skill: root cause analysis and RD confirmation for Bug tickets. Use when the user wants to triage, analyze, or diagnose a Bug ticket — before planning starts. Trigger: '修 bug', 'fix bug', '分析 bug', 'triage bug', 'bug 分析', '修這張 bug', 'help me fix', '幫我修正', '開始修正', '修正這張', 'fix this ticket' (when issue type is Bug), 'debug', '找 bug', '為什麼壞了', 'why is this failing', 'investigate', '查問題', '這個怎麼回事', 'root cause', '根因', '排查'. NOT for: PR review fixes (use engineering revision mode), already-diagnosed bugs with root cause confirmed (use breakdown → engineering). This skill handles DIAGNOSIS only — estimation, test plan, QA challenge, and design doc are delegated to breakdown.
HsuanYuLee/polaris · ★ 4 · AI & Automation · score 80

Install: claude install-skill HsuanYuLee/polaris

# Bug Triage — 診斷層 Bug ticket 的診斷入口：讀票、定位 project、找 root cause、讓 RD 確認，最後把已確認分析寫回 JIRA，交給 `breakdown` 派工。 ## Contract `bug-triage` 只做 diagnosis。不估點、不拆 task、不寫 Design Doc、不建 branch、不修 code、不開 PR。這些分別屬於 `breakdown` 與 `engineering`。若 ticket 不是 Bug，停止並路由：Story/Task 走 `breakdown` 或 `engineering`，Epic 走 `refinement` 再 `breakdown`。若 JIRA 已有 `[ROOT_CAUSE]`，詢問要重新分析或直接派工。 Bug 的 planning handoff 仍以 confirmed RCA 為前提，但 direct-to-`engineering` 只在已存在 authoritative task work order 時合法；沒有 work order 時，下一步一律是 `/auto-pass {BUG_KEY}`。 ## Reference Loading | Situation | Load | |---|---| | Any bug | `bug-triage-entry-flow.md`, `project-mapping.md`, `workspace-config-reader.md` | | AC verification failure bug | `bug-triage-acfail-flow.md`, `pipeline-handoff.md`, `handoff-artifact.md`, `worktree-dispatch-paths.md` | | Root cause analysis | `bug-triage-root-cause-flow.md`, `explore-pattern.md`, `repo-handbook.md`, `planning-worktree-isolation.md` as needed | | Confirmation and JIRA write | `bug-triage-confirm-handoff-flow.md`, `workspace-language-policy.md`, `external-write-gate.md` | Explorer sub-agent dispatch 必須注入 `sub-agent-roles.md` 的 Completion Envelope。Full path 與 AC-FAIL path 的 raw evidence 寫入 handoff artifact，供 downstream engineering on-demand 讀取。 ## Flow 1. Parse ticket key，讀 JIRA ticket，確認 issue type。 2. 依 `project-mapping.md` 與 workspace config 找 project，先讀 company handbook index + linked docs，再讀 repo handbook index + linked docs。 3. 若 ticket 來自 verify-AC `[VERIFICATION_FAI