decision-debateUse when presenting 2+ technical approaches, listing pros/cons, evaluating architecture or technology trade-offs, or when the user asks 'which should I choose'.
geminiUse when asked to 'gemini review', 'gemini challenge', 'ask gemini', or want an independent cross-model second opinion / adversarial review / consultation from a different AI vendor (Google's Antigravity CLI, `agy`) on a diff, plan, or codebase question.
kc-em-plan-reviewUse when reviewing a teammate's plan, Linear project/issue, design doc, or Slack-thread proposal AS the EM before build starts — applies Kent's EM lenses, verifies the single load-bearing assumption against real code, de-dups against existing reviews, runs a mandatory cross-model pressure-test, and
kc-em-syncUse when syncing team context (initiatives, projects, members, cycles, customers, estimate scale) from Linear to local YAML cache. Triggers on '/kc-em-sync', 'sync team context', 'refresh team data', '同步團隊資料', 'team sync'.
kc-em-triageUse when triaging Linear issues as EM — exploring codebase, researching tech feasibility, decomposing oversized issues, posting structured implementation guidance, or processing meeting notes into Linear Customer Requests/Needs.
kc-project-pulseThis skill should be used when the user asks to "update project status", "write pulse update", "draft weekly update", "post project pulse", "project 更新", "寫 pulse", "weekly update", or wants to draft and post Linear project status updates. Covers data collection, health assessment, drafting, and pos
kc-rules-reviewUse when the user wants to change their agent operating rules, says they keep correcting the same thing across projects, suspects a rule is being ignored, asks whether the rule file is too long, or asks which rules to delete. Also use after a rule change lands, when Claude and Codex user rules or do