skills/dispatch-strategy-review/SKILL.md
派發策略檢討工具. Use for: (1) 失敗數超預期 30% 時的策略檢討, (2) 重複分派失敗的分析, (3) 代理人選擇錯誤的修正
npx skillsauth add tarrragon/claude dispatch-strategy-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
版本: v1.1 建立日期: 2026-01-23 狀態: 穩定
派發策略檢討工具用於檢討和改進代理人派發策略,在派發失敗或效果不佳時進行系統性分析和調整。
以下情況應使用此 Skill:
| 情境 | 識別特徵 | 強制性 | |------|---------|--------| | 失敗數超預期 | 失敗數超過預期的 30% | 強制 | | 重複分派失敗 | 同一任務分派 2+ 次仍失敗 | 強制 | | 代理人選擇錯誤 | 派發後發現代理人不適合 | 建議 | | 效率低下 | 任務完成時間遠超預期 | 建議 |
派發策略檢討遵循 5 個 Stage 的結構化分析流程:
詳細模板: 見
references/stage-templates.md取得各 Stage 的完整輸出格式模板
見 references/full-report-template.md 取得完整報告模板,包含所有 5 Stage 的結構化報告格式。
見 references/common-dispatch-errors.md 取得常見派發錯誤識別和修正方法。
| Skill | 關係 |
|-------|------|
| /ticket track | 使用 ticket-track 收集失敗任務資訊 |
| /5w1h-decision | 改進措施應符合 5W1H 格式 |
| /pre-fix-eval | 如果失敗涉及錯誤修復,使用 pre-fix-eval |
Last Updated: 2026-03-02 Version: 1.1.0 - 移除不支援的自訂屬性,採用 Progressive Disclosure
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
development
Claude Code release notes 框架影響評估工具。比對 last-reviewed 版本篩出新版本,逐項分類(對框架有幫助 / 需評估 / 無影響 / 不適用),對採用項引導建 ANA + WRAP + spawn 落地。Use when: 執行 /release-notes 看到新版本、定期檢查 CC 更新、評估新功能對專案框架的影響時。Triggers: release notes, release-notes, CC 更新, claude code 更新, 版本更新評估, 新功能評估, 框架影響評估。
development
Assertion design judgment framework for flaky and design-quality issues. Use when writing tests, reviewing assertions, diagnosing flaky tests, or deciding if a timing/float/cache assertion is appropriate. Do NOT use for API syntax or refactoring.
tools
Chrome Extension 實機測試與 debug 工作流,以 chrome-devtools-mcp 為核心工具。Use when: (1) 完成功能後實機驗證 / manual test / 試看看 / 跑看看 / verify feature, (2) extension debug / popup 不作動 / content script 不注入 / service worker 報錯 / background 出問題, (3) 安裝 unpacked extension / load unpacked / 載入未封裝, (4) 看 console / 看 network / 看 log / view console / inspect requests, (5) 功能更新後重新載入 extension / rebuild reload / reload extension。涵蓋 Manifest V3 service worker / content script / popup / options page 的 chrome-devtools-mcp 工具呼叫流程。不取代 Puppeteer / Playwright 自動化 E2E(CI 用),定位為開發期手動驗證與 LLM-assisted debug。