mckinsey-skills

Plugin mckinsey-skills from marketplace mckinsey-skills in subhashdasyam/mck-skills. Commands read from the repo's manifest — 1 month ago.

Skills (22)

• 7s-framework

  Use when the user says "7S", "7-S", "organizational alignment", "post-merger integration check", "diagnose the org", "why is execution failing", "org design", "is our strategy aligned with our structure", "do we have the right capabilities", "culture change", or "integration risk". The 7S Framework

• business-system

  Use when the user says "value chain", "business system", "where do we win in the value chain", "operating model", "which stage creates the most value", "where is our advantage in the chain", "activity system", "what are our core activities", "where are we vertically integrated", or "which stages sho

• consumer-decision-journey

  Use when the user says "customer journey", "consumer decision journey", "purchase funnel", "consider evaluate buy", "loyalty loop", "moments of truth", "where do we lose customers", "where is the biggest drop-off", "how do customers decide", "trigger to purchase", "post-purchase experience", "brand

• ge-mckinsey-matrix

  Use when the user says "GE matrix", "nine-box", "nine box", "portfolio prioritization", "harvest or divest", "which BUs to invest in", "allocate capital across business units", "portfolio review", "which businesses to grow vs. exit", "industry attractiveness", or "competitive position". The GE-Matri

• growth-strategy

  Use when the user says "how do we grow", "growth strategy", "growth options", "core adjacency new", "Ansoff matrix", "growth runway", "5-year growth plan", "where should we invest to grow", "organic vs inorganic growth", "new markets new products", "expand the business", or "what are our growth leve

• hypothesis-driven

  Use when the user wants to "form a hypothesis", "prove or disprove", "hypothesis-driven approach", "what would have to be true", "answer-first analysis", "test the answer first", "start with an answer", "where should we focus", "what is your hypothesis", or "ghost deck". The hypothesis-driven approa

• industry-cost-curve

  Use when the user says "cost curve", "industry cost curve", "supply curve", "where do we sit on the cost curve", "low-cost producer", "cost position", "shutdown price", "price floor", "who sets the marginal price", "cost competitiveness", "which producers get squeezed when price falls", or "cost sta

• influence-model

  Use when the user says "change management", "drive adoption", "behavior change", "make it stick", "why is the change not sticking", "role modeling", "mindset shift", "culture change", "post-merger culture", "people are resistant", "employees won't adopt", "how do we get buy-in", "transformation", "c

• issue-trees

  Use when the user wants to "build an issue tree", "decompose this problem", "what are the drivers of X", "root cause tree", "logic tree", "tree this out", "drill down on this issue", "break the problem into branches", "what are the branches", or needs to recursively break a question into testable su

• market-entry

  Use when the user says "should we enter this market", "new geography", "new market segment", "new product category", "build buy or partner", "go to market strategy", "market expansion", "is this market attractive", "can we win here", or "entry strategy". The Market Entry framework applies a four-tes

• market-sizing

  Use when the user says "how big is the market", "TAM SAM SOM", "Fermi estimate", "top-down vs bottom-up", "market size", "addressable market", "total addressable market", "estimate the market", "how many units", "how much does the market spend", or "size the opportunity". The Market Sizing framework

• mece

  Use when the user needs to structure a problem, "break this down", "create buckets", "decompose a question", "ensure no overlap or gaps", "split into categories", "what are the dimensions", "is this MECE", or "are these exhaustive". The foundational structuring skill that validates any categorizatio

• mergers-acquisitions

  Use when the user says "should we acquire", "M&A", "merger", "acquisition", "synergies", "deal valuation", "integration risk", "build vs buy", "strategic fit", "due diligence", "accretive or dilutive", "what would we pay", or "post-merger integration". The M&A framework evaluates any deal across fou

• portfolio-of-initiatives

  Use when the user says "initiative portfolio", "familiarity matrix", "stretch initiatives", "kill or scale", "portfolio of bets", "which initiatives should we invest in", "balance risk across initiatives", "near-in vs. step-out", "core vs. adjacent vs. new", or "prioritize our growth initiatives". T

• pricing

  Use when the user says "pricing strategy", "set the price", "what should we charge", "raise prices", "price increase", "willingness to pay", "WTP", "discount strategy", "price elasticity", "tiered pricing", "value-based pricing", "cost-plus pricing", "price optimization", or "how do we capture more

• profitability

  Use when the user says "why are profits down", "margin decline", "margin compression", "revenue vs cost", "EBITDA fell", "where is the leak", "profit is shrinking", "what's driving the profit drop", "diagnose the P&L", "revenue decline", "cost overrun", or "operating leverage". The Profitability fra

• pyramid-principle

  Use when the user needs to "structure my report", "executive summary structure", "write the memo", "top-down communication", "synthesize my findings", "pyramid principle", "BLUF", "lead with the answer", "what is my main message", "governing thought", "rule of three", "key lines", or "format this fo

• router

  Top-level orchestrator for structured business problem-solving, strategy work, and executive communication. Use when diagnosing a business problem, sizing a market, planning a market entry, evaluating an M&A target, setting pricing, building a growth strategy, allocating a portfolio of initiatives,

• scr-storyline

  Use when the user needs to "frame the question", "structure the narrative", "situation complication resolution", "SCR", "storyline", "narrative arc", "SCQA", "set the context", "build the case", or "frame the problem before solving it". SCR-Storyline opens communication with three beats - Situation

• seven-step-process

  Use when the user wants a "structured problem solving" approach, "end-to-end case", "seven step", "full problem-solving cycle", "from problem to recommendation", "walk me through this systematically", "I have a vague problem", or "how do I tackle this". The seven-step process drives a problem throug

• strategic-control-map

  Use when the user says "strategic control", "market-to-book", "economic moats", "moat analysis", "long-run competitive advantage", "who has pricing power", "which competitors compound value", "sustainable advantage", "competitive position over time", or "which businesses deserve premium valuation".

• three-horizons

  Use when the user says "three horizons", "H1 H2 H3", "core adjacent transformational", "growth runway", "defend the core", "build emerging businesses", "portfolio balance across time", "are we over-invested in the core", "what's our growth pipeline", or "long-run growth strategy". The Three Horizons

Slash commands (2)

• /mckinsey-skills:mck-solve

  Structured problem-solving using the mckinsey-skills framework chain. Routes the problem through the right frameworks (MECE, issue trees, hypothesis-driven analysis, profitability, market entry, pricing, growth strategy, and more) and produces coaching markdown, filled ASCII/Mermaid templates, and a

• /mckinsey-skills:mck-synthesize

  Turn raw findings, bullet points, or analysis outputs into an executive-ready structured memo. Skips problem structuring - goes straight to SCR storyline then Pyramid report. Use when you already have findings and need to communicate them, not when you need to structure a problem.

Similar plugins