From business-strategy
Use when evaluating high-stakes decisions with bias-aware quality control, including proposal review, decision meeting facilitation, and personal coaching. Trigger on requests such as 重大決策、偏誤檢查、提案審查、決策會議引導、決策教練、go/no-go 決策。
How this skill is triggered — by the user, by Claude, or both
Slash command
/business-strategy:decision-bias-quality-controlThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
使用此技能來執行「決策品管」,把重大決策從直覺推進到可追溯、可檢查、可比較的判斷流程。
使用此技能來執行「決策品管」,把重大決策從直覺推進到可追溯、可檢查、可比較的判斷流程。
遵循兩個核心原則:
先閱讀下列參考檔:
接收下列結構化輸入;欄位不足時走 Data Sufficiency Gate。
mode: proposal-review | meeting-facilitation | personal-coaching | autodecision_statement: string(必要)decision_context: string(必要)proposal_snapshot: string(提案審查時建議提供)decision_size_factors:
financial_impact: 1|2|3reversibility: 1|2|3org_blast_radius: 1|2|3若 mode=auto,依需求語意路由:
proposal-review。meeting-facilitation。personal-coaching。若語意混合,先以 proposal-review 執行主流程,並在附錄提供會議引導問題。
先檢查必要欄位:
decision_statementdecision_context再檢查評分所需欄位:
decision_size_factors.financial_impactdecision_size_factors.reversibilitydecision_size_factors.org_blast_radius缺資料時,輸出 MissingDataOutput:
missing_fieldswhy_neededquestions_to_usertemporary_assumptionrisk_of_assumption預設規則:
decision_size=Medium,並標註風險。每次輸出都必須同時包含以下兩軌,不得省略其中任一軌。
bias_diagnosis: 偏誤診斷摘要(依 12 問分組)key_risks: 3-5 個核心風險(附證據來源)recommended_actions: 3-5 個可執行行動(含優先級)question_scores: 12 題逐題分數(0|1|2)與簡要理由group_scores: 三組標準化分數(0-100)weighted_total_score: 加權總分(0-100)decision_size: Low|Medium|Highrisk_level: Green|Yellow|Redthreshold_profile_used: 對應門檻表依 references/04-scoring-thresholds.md 計算,使用固定模型:
0|1|230%40%30%proposal-review: 輸出 go | conditional-go | no-go。meeting-facilitation: 輸出會議腳本、追問順序、決策收斂規則。personal-coaching: 輸出選項比較、偏誤提醒、48 小時驗證行動。詳見 references/03-mode-workflows.md。
Use $decision-bias-quality-control to evaluate this high-stakes decision in dual-track mode with full 12-question scoring and dynamic risk thresholds.
npx claudepluginhub timlai666/skills --plugin business-strategyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.