菜单
Use when the user wants to generate a daily standup report or end-of-day summary (YDY/TDT/BOS/口頭同步). Single entry point for all standup and end-of-day workflows. Trigger: 'standup', '站會', 'daily', '寫 standup', '下班', '收工', 'EOD', 'wrap up', '今天做了什麼'.
用 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 | standup |
| description | Use when the user wants to generate a daily standup report or end-of-day summary (YDY/TDT/BOS/口頭同步). Single entry point for all standup and end-of-day workflows. Trigger: 'standup', '站會', 'daily', '寫 standup', '下班', '收工', 'EOD', 'wrap up', '今天做了什麼'. |
| metadata | {"author":"Polaris","version":"2.1.0"} |
從 git、JIRA、Calendar、PR status、triage state 與使用者補充資料產出 YDY / TDT / BOS / 口頭同步報告。使用者確認後，先存 local markdown，再 append 到 Confluence standup page。
standup 是 daily standup 與 EOD summary 的單一入口。它可以自動觸發當日 triage guard，
但不取代 my-triage 的排序判斷，也不捏造資料來源沒有的活動。
它可以轉述 PR / JIRA / planning / blocker 現況，但不得自行把這些訊號升格成 workflow
authority；例如「PR 狀態良好」不等於 mergeable_ready，release page / standup 內容也不等於
release eligibility 或 release completed。
Confluence 寫入前必須等待使用者確認。沒有 blockers 時保留 BOS heading，不寫「無」。
| Situation | Load |
|---|---|
| Any run | standup-data-collection-flow.md, workspace-config-reader.md, shared-defaults.md |
| TDT / planning | standup-planning-flow.md, session-timeline.md when useful |
| Formatting / publish | standup-format-publish-flow.md, standup-template.md, confluence-page-update.md, workspace-language-policy.md |
| Monthly framework hygiene | framework-iteration-procedures.md, repo-handbook.md if first monthly standup needs framework follow-up |
my-triage，讓使用者確認。YDY_DATE、PRESENT_DATE、TDT_PLAN_DATE；使用者指定日期時以使用者為準。mise run closeout-drift（呼叫
scripts/detect-closeout-drift.sh --dry-run --json，report-only，不變更 specs）取得：把
delivered-drift-high（已交付未 archive，可排入 closeout）與 stranded（LOCKED 過期無交付
證據，需 review）併入 TDT candidate；delivered-drift-low 列為待確認。gh 不可用時 report
會標 PR 證據未檢，轉述該註記、不視為失敗。standup-template.md 組裝四區塊並呈現給使用者確認。[KEY title](URL) markdown，不使用 Confluence smartlink custom tags。PRESENT_DATE；TDT work target 才是 next Monday。confluence-page-update.md 做 search、version check、append。workspace-language-policy.md。輸出 standup date、YDY/TDT/BOS counts、local file、Confluence status、任何 skipped sources 與原因。
Execute post-task-reflection-checkpoint.md before reporting completion.