This skill should be used when the user asks to "set targets for the scorecard," "what initiatives support this objective," or needs each measure given a target and each objective checked against whether a real program of work is actually driving it.
Stakeholder impact mapping, change readiness assessment, sponsor roadmaps, communications planning, and resistance diagnosis — the people side of transformation, separate from program governance and operating model design.
This skill should be used when the user asks "are we ready for go-live," "assess change readiness," "what is the binding constraint on adoption," or needs a structured readiness scorecard before sponsor or steering decisions.
This skill should be used when the user asks for a "change comms plan," "communications calendar for this transformation," "what do we tell each audience and when," or needs audience × message × channel × timing before go-live.
This skill should be used when the user describes "resistance to the change," "people pushing back," "adoption stalling," or "blockers on the people side" and needs root-cause split and response options before escalation or comms rework.
This skill should be used when the user asks for a "sponsor roadmap," "what should the executive sponsor do and when," "sponsor engagement plan," or needs visible sponsor actions aligned to program phases and readiness gaps.
This skill should be used when the user asks to "map stakeholders for this change," "who is affected and how," "build a stakeholder impact analysis," or needs influence/impact segmentation with specific behavior and process changes before readiness assessment or comms planning.
This skill should be used when the user asks to "outline a deck on X," "what's the storyline for this deck," "build a slide-by-slide outline," or needs a presentation structured before any actual slide design happens.
This skill should be used when the user asks to "review this deck for structure," "critique this memo," "is this narrative tight," or provides an existing document or deck and wants a structural critique against pyramid and so-what discipline rather than a line edit or rewrite.
This skill should be used when the user asks to "write an exec memo," "BLUF this," "turn this into a one-pager," or needs a narrative or raw notes condensed into a conclusion-first executive memo.
This skill should be used when the user asks to "build a hypothesis tree," "structure this as an issue tree," "what are our hypotheses for X," or presents a problem statement that needs to be broken into falsifiable sub-hypotheses before analysis starts.
This skill should be used when the user asks to "build a narrative from these notes," "what's my storyline here," "structure this into a pyramid," or provides raw findings, interview notes, or analysis output and wants it turned into a governing thought with supporting argument structure.
This skill should be used when the user asks to "run a pre-mortem on this decision," "red-team this recommendation," "what could kill this strategy," or has a near-final option, deal, or program that needs dis-confirming evidence, devil's-advocate challenge, and decision-quality scoring before commitment.
This skill should be used when the user asks to "forecast this project using reference class," "apply outside-view to this estimate," "calibrate optimism bias on this business case," or has cost, duration, or benefit estimates that need Flyvbjerg-style outside-view benchmarking and HM Treasury Green Book optimism-bias…
This skill should be used when the user asks "what's the so-what here," "sharpen this insight," "this is just facts, what does it mean," or provides a list of observations or data points that need to be turned into insight statements.
This skill should be used when the user asks to "turn this into a workplan," "build a hypothesis-driven workplan," "who's doing what on this analysis," or has a hypothesis tree (from this plugin or elsewhere) that needs owners, timelines, and data sources attached.
This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.
This skill should be used when the user asks to "assess our growth options," "where should our growth come from," "build a growth strategy," or has a portfolio of growth initiatives that need to be checked against a real growth target — not just sorted into categories.
This skill should be used when the user asks "should we build this, acquire it, or partner for it," has a capability gap that needs a build/buy/partner decision, or wants that decision checked against the known failure pattern each path tends toward.
This skill should be used when the user asks to "evaluate this strategic option," "should we make this move," "build the case for/against this deal," or has a major strategic decision (market entry, M&A, large capital commitment) that needs real-options framing rather than a binary go/no-go.
This skill should be used when the user asks "should we exit this business," "is this worth continuing to fund," "do a portfolio pruning review," or needs an explicit exit/hold/double-down call on a unit — with sunk-cost reasoning named directly when it appears.