AI Agent Workflow Collection

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.

Use when the user wants to set up or sync Codex MCP servers for Polaris workflows. Trigger: 'codex mcp', '同步 mcp', '設定 codex mcp', '讓 codex 接 mcp', 'codex mcp setup'.

Use when the user wants a prioritized view of all currently assigned work (Epics, Bugs, Tasks/Stories) to decide what to work on next, or needs a zero-input 'what should I do next' entry point (brain blank, returning from break, context switch). Also handles cross-session resume scan (MEMORY.md Hot + recent checkpoints + wip/ branches + branch-ticket). Trigger: '我的 epic', 'my epics', '盤點', 'triage', '手上有什麼', 'my work', '我的工作', '排優先', '下一步', '繼續', '然後呢', 'what''s next', 'next', '接下來', '推進手上的事情' (when no ticket key / topic keyword follows).

Slack collaboration layer: extracts PR URLs from Slack messages and dispatches to engineering revision mode. Does NOT modify code — all code changes, GitHub review replies, and lesson extraction are engineering's responsibility. Trigger: "pr-pickup", "pickup", Slack URL + PR intent ("pickup ", "處理 ", "同仁貼的 ", "接這個 PR "). NOT for: reviewing others' PRs (use review-pr), first-cut implementation (use engineering directly), fixing your own PR without Slack context (use engineering with ticket key or PR URL directly).

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.

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 ', '幫我看這串'). Key: '我的 PR' → check-pr-approvals; '大家的 PR' / Slack URL → here; single PR URL → review-pr.

Generates a SA/SD (System Analysis / System Design) document for a JIRA ticket — a structured implementation plan produced before coding begins. Use this skill whenever the user mentions SASD, SA/SD, 寫 SA, 出 SA/SD, SA 文件, SD 文件, 架構文件, implementation plan, 系統分析, 系統設計, 技術設計, 異動範圍, dev scope, design doc, technical design, or asks to analyze what changes are needed for a ticket, plan the implementation approach, or produce a technical design document — even if they don't explicitly say "SA/SD".

Sets the active company context or diagnoses company routing. Two modes: (1) Set — declare which company to work with, bypassing auto-detection. (2) Diagnose — show which company a JIRA ticket or project routes to. Trigger keywords: "use company", "switch company", "切換公司", "用這間", "/use-company", "set company", "公司切換", "我要做 X 公司的", "which company", "哪間公司", "/which-company".

QA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUALREQUIRED/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, transitions the AC ticket to Done. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to bug-triage; spec issue routes back to refinement.