My triage
A Claude Code workspace template with AI skills for JIRA, PRs, code review, estimation, and daily standups
npx -y skills add HsuanYuLee/polaris --skill my-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
個人工作盤點與 zero-input next router；列出 assigned Epics/Bugs/Tasks，整合 cross-session resume signals，協助決定下一步。
SKILL.md
3.7 KB, as published. Nobody here has run it
My Triage
my-triage 是個人工作 dashboard 與 zero-input router，用於「下一步 / 繼續 / 手上有什麼」
這類沒有明確 ticket/topic 的情境。
Contract
my-triage 只讀取並排序個人工作，不施工、不估點、不改 JIRA status。若使用者說「繼續
DP-015」或「繼續 PROJ-123」這類帶明確 topic 的句子，不攔截；交給 active skill /
cross-session continuity 解析。
它屬於 mixed reader / next-step orchestrator：workspace config 與 resume signals 只用來
決定 dashboard scope、排序、與 route suggestion。my-triage 可以推薦下一步，但推薦不等於
workflow transition、verification result、release readiness、或 author-side completion
authority。
Reference Loading
| Situation | Load |
|---|---|
| Any run | my-triage-resume-flow.md, workspace-config-reader.md, shared-defaults.md, jira-story-points.md |
| Dashboard scan | my-triage-dashboard-flow.md, stale-approval-detection.md |
| State write / standup handoff | my-triage-state-flow.md, session-timeline.md |
| Large GitHub scan | sub-agent-roles.md Completion Envelope |
Flow
- Resolve workspace config and current git context.
- Run resume scan first: branch-ticket, Hot memory, recent checkpoints, WIP branches.
- Fetch assigned active Epics, Bugs, and orphan Tasks/Stories.
- Verify status category and remove completed/status-mismatched items.
- Add GitHub progress for In Development items.
- 排成 resume candidates、Bugs、In Development、priority-based todo groups。
- 盤點 DP closeout drift（report-only）：跑
mise run closeout-drift（呼叫scripts/detect-closeout-drift.sh --dry-run --json，不變更 specs）。把delivered-drift-high/delivered-drift-low/stranded結果併入 dashboard 的 「closeout drift」群組，讓使用者看到已交付卻從未 archive 的 LOCKED DP，或 LOCKED 後 過期且無交付證據的 DP。gh不可用時 report 會標 PR 證據未檢——轉述該註記，不視為失敗。 - Render dashboard and write compact
.daily-triage.jsonin the same pass. - Recommend next routes：
engineering、breakdown、check-pr-approvals、sprint-planning，或 explicit topic resume。closeout-drift findings 的建議：delivered-drift-high建議走framework-releasecloseout / archive；delivered-drift-low/stranded建議人工 review（絕不自動 archive——detector 本身只 report）。
Hard Rules
- Cross-session resume candidates appear before current-day work.
- Bug group appears before normal Epic/Task work, except resume candidates.
- If today's triage state already exists, ask before rescanning.
- Do not scan child Tasks/Stories already covered by an Epic.
- Do not repeat Session Start Fast Check file lists; cite them briefly.
- Do not auto-modify JIRA or GitHub.
.daily-triage.json是 local planning state，不是 shared workflow state；不得把其中的 rank / progress 直接包裝成mergeable_ready、release_eligible、release_completed、 或其他 deterministic gate 結果。- 大型 GitHub scans 可使用 sub-agents，但必須 read-only，並回傳 Completion Envelope。
Completion
Return active counts, excluded status-mismatch items, ranked dashboard, suggested next action, triage state write status, and any blocked data sources.
Post-Task Reflection (required)
Execute post-task-reflection-checkpoint.md before reporting completion.