my-triage
Solid個人工作盤點與 zero-input next router;列出 assigned Epics/Bugs/Tasks,整合 cross-session resume signals,協助決定下一步。
Install
Quality Score: 80/100
Skill Content
Details
- Author
- HsuanYuLee
- Repository
- HsuanYuLee/polaris
- Created
- 4 months ago
- Last Updated
- 3 days ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
intake-triage
批次收單排工:分析 PM 開出的一批 ticket,評估優先序,告訴 PM 哪些先做、哪些後做、哪些規格不足需補。 產出 JIRA label + comment + Slack 摘要。 觸發:「收單」、「排工」、「intake」、「這批單幫我看」、「PM 開了一堆單」、「幫我排優先」、 「intake-triage」、「triage these tickets」、「prioritize this batch」。 當使用者提供一批 ticket key 並要求排優先序時使用此 skill,不要與 /my-triage(個人每日盤點)混淆。
converge
Use when the user wants to push all in-flight work forward toward review in one pass — closing gaps across Epics, Bugs, and orphan Tasks. NOT for single-ticket work (use engineering) or read-only triage (use my-triage). Trigger: '收斂', 'converge', '推進', '全部推到 review', '把我的單收一收', 'epic 進度', '離 merge 還多遠', '補全'.
pipeline-triage
Runs Stage-2 Triage over the platform's improvement backlog — reads `status: proposed` GitHub Issues, executes the Phase-A analysis sequence (A1–A6.5: DoR completeness, duplicate/subsumption + similarity, dependency-state validation + native-dep mirror, feasibility, priority re-evaluation, oversize routing, per-issue summary, management-task signals), and produces ONE consolidated triage summary with a per-issue Approve/Defer/Reject recommendation. Auto-execute is the operative default: the A1–A6 enrichment runs end-to-end without per-action approval; only the state-mutating Close/Reject requires operator confirmation, and the Approve/Defer/Reject verdict itself stays operator-only (Tier 3). Reads the pipeline improvement backlog, not the Jira / project delivery backlog. Triggers: "triage the proposed queue", "run Stage-2 triage", "triage the improvement backlog", "run the triage analysis on the proposed issues", "what's the triage recommendation for the proposed backlog".