菜单
批次收單排工：分析 PM 開出的一批 ticket，評估優先序，告訴 PM 哪些先做、哪些後做、哪些規格不足需補。 產出 JIRA label + comment + Slack 摘要。 觸發：「收單」、「排工」、「intake」、「這批單幫我看」、「PM 開了一堆單」、「幫我排優先」、 「intake-triage」、「triage these tickets」、「prioritize this batch」。 當使用者提供一批 ticket key 並要求排優先序時使用此 skill，不要與 /my-triage（個人每日盤點）混淆。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to discover and review PRs across the team awaiting their attention. NOT for a single specific PR (use review-pr). Supports three discovery modes: Label (GitHub label scan), Slack (channel-wide scan), Thread (specific Slack thread URL). Trigger: '掃 PR', 'review 大家的 PR', '批次 review', '有哪些 PR 要我看', Slack thread URL + review intent ('review <slack_url>', '幫我看這串'). Key: '我的 PR' → check-pr-approvals; '大家的 PR' / Slack URL → here; single PR URL → review-pr.
掃描使用者的 open PR，偵測 CI 狀態、未回覆 review comments、approval 數量，分類為三種狀態（可催/需修/已達標）後由使用者選擇催 review 或手動修正。Trigger: '我的 PR', 'check PR approvals', 'PR 狀態', '催 review', '催 PR', 'PR 被 approve 了嗎', '幫我掃我的 PR', '請同仁 review', '請同仁幫我 review', '請大家 review', '請大家幫我 review', '請大家幫忙看一下', '找人 review', '找誰 review', '請[人名/角色]幫我 review', '請[人名/角色]幫忙看 PR'. 主語為同仁/大家/人名/角色的「請X幫我 review」屬於催 review 範疇，不要 route 到 review-pr。
Universal planning skill: Bug reads ROOT_CAUSE then estimates; Story/Task/Epic explores codebase then splits into sub-tasks with estimates, and packs each sub-task into a self-contained task.md work order for engineering to consume. Also handles scope challenge (advisory mode). Trigger: 拆單, 'split tasks', 拆解, 'breakdown', 'break down', 子單, 'sub-tasks', 評估這張單, 'evaluate this ticket', 估點, 'estimate', 'scope challenge', '挑戰需求', 'challenge scope', '需求質疑'.
Iteratively enriches incomplete JIRA Epics into estimation-ready, technically-validated specs. Five modes: batch readiness scan, RD discovery (Phase 0), PM elaboration (Phase 1), technical approach (Phase 2), and multi-round iteration. Phase 1 goes beyond checklist filling — it explores the codebase, hardens AC, and produces a structured artifact for downstream skills. Trigger: "refinement", "grooming", "討論需求", "需求釐清", "補完 Epic", "這張單缺什麼", "brainstorm", "方案討論", "想重構", "tech debt", "batch refinement", "sprint prep", or Epic with sparse content needing enrichment.
QA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents observed vs expected as pure facts (no root-cause judgement). On FAIL, surfaces human disposition gate (spec issue vs implementation drift); on PASS, it may transition the AC ticket to Done only after verification artifact/report is current and the shared verification contract resolves to PASS. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to refinement Bug source mode; spec issue routes back to refinement.
Canonical main-chain orchestrator for locked/current refinement-owned sources (DP-backed or JIRA Epic-backed). It routes a source through breakdown, engineering, and verify-AC without taking over their mutation authority. Trigger: "auto-pass {KEY}", "快速通關 {KEY}", "完整流程 {KEY}" when the source is LOCKED and artifacts are current. `{KEY}` 可以是 `DP-NNN` 或 JIRA Epic key。
| name | intake-triage |
| description | 批次收單排工：分析 PM 開出的一批 ticket，評估優先序，告訴 PM 哪些先做、哪些後做、哪些規格不足需補。 產出 JIRA label + comment + Slack 摘要。 觸發：「收單」、「排工」、「intake」、「這批單幫我看」、「PM 開了一堆單」、「幫我排優先」、 「intake-triage」、「triage these tickets」、「prioritize this batch」。 當使用者提供一批 ticket key 並要求排優先序時使用此 skill，不要與 /my-triage（個人每日盤點）混淆。 |
| metadata | {"author":"Polaris","version":"2.1.0"} |
批次分析 PM 開出的 tickets，產出「先做 / 後做 / 補規格 / 不建議做」的排序建議， 並可寫回 JIRA labels/comments 與 Slack 摘要。
intake-triage 是 batch intake prioritization，不是個人每日工作盤點（my-triage），
也不是深入 refinement、sprint planning、或 engineering codebase probe。
它屬於 mixed reader / writeback orchestrator：workspace config、ticket content、與 batch
signals 只用來決定 prioritization verdict、rank、與 downstream suggestion。intake-triage
可以產出 JIRA labels/comments 與 Slack summary，但這些 writeback 只代表 intake guidance，
不等於 workflow transition、implementation readiness、verification result、或 release
authority。
它只依 ticket 內容與同批關係做快速排序；不做 codebase exploration、不自動改 status、 不把 intake comment 當 implementation spec。
| Situation | Load |
|---|---|
| Any run | intake-triage-input-flow.md, workspace-config-reader.md, shared-defaults.md, jira-story-points.md |
| Scoring | intake-triage-scoring-flow.md, epic-template.md |
| Writeback / Slack summary | intake-triage-writeback-flow.md, workspace-language-policy.md, slack-message-format.md |
Per-ticket analysis 或 JIRA writeback 派 sub-agent 時，必須注入 sub-agent-roles.md 的
Completion Envelope。
intake-* labels 與 intake comment。workspace-language-policy.md。intake- prefix，不碰其他 labels。輸出 batch count、verdict counts、top ranks、writeback status、Slack status、blocked/skipped
questions，以及後續路由：my-triage、sprint-planning、refinement、或 engineering。
Execute post-task-reflection-checkpoint.md before reporting completion.