From business-strategy
Use when analyzing a group, business-unit, product-line, or brand portfolio with the BCG growth-share matrix, especially when the task involves relative market share, market growth, quadrant classification, capital allocation, portfolio prioritization, or deciding whether to invest, maintain, harvest, reposition, or exit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/business-strategy:bcg-growth-share-matrixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
用 BCG 成長佔有率矩陣分析集團或產品組合,將各事業體依 `relative market share` 與 `market growth rate` 放入四象限,並產出資本配置、風險說明與後續追蹤動作。
用 BCG 成長佔有率矩陣分析集團或產品組合,將各事業體依 relative market share 與 market growth rate 放入四象限,並產出資本配置、風險說明與後續追蹤動作。
此 skill 預設以繁體中文輸出,但保留 Cash Cows / Stars / Question Marks / Dogs 英文對照。把 BCG 當成投資組合篩選器,不把它當成唯一決策器。
Use when:
BCG matrix、growth-share matrix、relative market share、market growthPets、Problem Child、Wild Cat、搖錢母牛投資 / 維持 / 收割 / 退出 / 重定位 之間做組合判斷Do not use:
必要輸入:
group_context: 集團簡述、戰略目標、資金限制、時間範圍business_units[]: 至少 2 個事業體或產品business_unit 至少包含:
namemarket_sharelargest_competitor_share 或 relative_market_sharemarket_growth_rate建議補充:
revenue_sizecash_generationstrategic_synergycompetitive_moatcapex_intensitytime_horizonthresholdsthresholds 若有提供,優先使用:
{
"relative_market_share_cutoff": 1.0,
"market_growth_cutoff": 10.0,
"borderline_band": 2.0
}
資料不足時不要直接硬分類,先輸出 MissingDataOutput:
{
"missing_fields": [],
"why_needed": {},
"questions_to_user": [],
"temporary_assumptions": [],
"assumption_risks": [],
"next_step_rule": "若缺口影響象限判定或資本建議,先補資料再分析;若可暫時假設,必須顯示假設與風險。"
}
缺資料時的規則:
largest_competitor_share 且無 relative_market_share,不可假裝能精準判定競爭力borderline,不要用武斷口吻分類時固定先做以下步驟:
relative_market_sharerelative_market_share,直接使用relative_market_share = market_share / largest_competitor_share
relative_market_share >= 1.0 預設視為高 sharemarket_growth_rate > 10% 預設視為高 growthborderline_band 內,要加註敏感度與替代判讀high share + high growth -> Starshigh share + low growth -> Cash Cowslow share + high growth -> Question Markslow share + low growth -> Dogshigh: 可見成長與份額改善路徑,且資本效率可接受medium: 可改善但有關鍵風險未解low: 份額/經濟性/協同任一核心條件不足cash_generation、strategic_synergy、competitive_moat、capex_intensityexception note輸出物件固定包含:
portfolio_snapshotmatrix_plot_dataunit_classification_tablequadrant_recommendationscapital_allocation_actionsportfolio_rebalance_prioritiesassumptions_and_limitationsnext_90_day_followupsportfolio_snapshotmatrix_plot_data固定欄位:
x_axis: relative_market_sharey_axis: market_growth_ratequadrant_cutoffspoints[],每筆包含:
namexyquadrantborderlineunit_classification_table每個事業體固定欄位:
namemarket_sharelargest_competitor_sharerelative_market_sharemarket_growth_ratequadrantclassification_reasonborderline_or_exceptiondevelopment_potentiallikely_transition_pathtransition_conditionstrategy_posturecapital_priorityquadrant_recommendations依四象限分組,說明:
capital_allocation_actions至少包含:
Cash Cows 應提供資金Stars 應優先防守或擴張Question Marks 應做階段式實驗Dogs 應收割、出售、關閉或僅因協同而保留portfolio_rebalance_priorities固定用:
Now (0-30 days)Next (31-90 days)Later (90+ days)assumptions_and_limitations固定包含:
next_90_day_followups至少列出:
relative_market_share 的來源或計法market_growth_cutoff,未提供時說明暫用 10%matrix_plot_data,且每個事業體都要有座標點likely_transition_path 與 transition_conditionDogs 不得一律直接判死刑;若存在協同、平台入口、法規牌照、防禦價值,需說明例外Question Marks 不得一律說「加碼」;必須加入投資條件與停損條件Cash Cows 不得只寫「維持」;要說明要不要擠現金、是否有被技術或需求轉移侵蝕的風險Stars 不得只寫「投資」;要說明是防守份額、加速滲透還是提升經濟性assumptions_and_limitationsUse $bcg-growth-share-matrix to analyze a group or product portfolio in Traditional Chinese, classify each business into Cash Cows, Stars, Question Marks, or Dogs, show the relative market share logic, and recommend portfolio-level capital allocation with caveats and next-step actions.
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.