claude-for-strategy

Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.

Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.

Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.

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 "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.

This skill should be used when the user asks to "turn these numbers into a narrative," "write up our performance for the board," or provides metrics or tracker results that need to become a readable, BLUF-structured narrative rather than a table of numbers.

This skill should be used when the user asks to "build me a metrics tracker," "wire up a daily log to the summary sheet," "create a performance tracker spreadsheet," or needs an actual spreadsheet built that replicates a Daily Log / summary-sheet pattern with formulas wired between tabs.

This skill should be used when the user asks to "build the business case for this transformation," "write up the cost-benefit for this initiative," or needs scope, cost, benefit, sequencing, risk, and a specific ask pulled together into a decision-ready business case.

This skill should be used when the user asks to "track this period's benefits," "update the register against actuals," "are we actually getting the savings we claimed," or needs a periodic remeasurement against baseline with an explicit attribution call — distinct from a status report, which tracks delivery progress, not realised value.

This skill should be used when the user asks to "build our strategy map," "draft objectives for the scorecard," "what's our causal chain," or has candidate objectives that need an explicit causal mechanism linking each one to the perspective above it — the actual intellectual core of a balanced scorecard, not just objectives sorted into four boxes.

This skill should be used when the user asks to "cascade the scorecard to business units," "build a team-level scorecard," or needs corporate strategy-map objectives translated into business-unit or team scorecards via a genuine causal-mechanism test, not just contribution-counting.

This skill should be used when the user asks to "define our perspectives," "set up our scorecard structure," "should we use the standard four perspectives," or needs to decide the perspective set and causal-chain order before any objectives get drafted.

This skill should be used when the user asks to "review the scorecard," "how are we tracking against the strategy map," "run our quarterly BSC review," or needs measures scored against targets AND the strategy map's causal links tested against what actually happened — the distinctively BSC discipline that separates a failed initiative from a failed theory.

This skill should be used when the user asks to "select measures for these objectives," "what should we measure for this," or needs each strategy-map objective assigned 1-3 measures with an explicit lead/lag classification and a check on the overall measure portfolio.

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.

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 uplift before approval.

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 "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.

This skill should be used when the user asks "how will competitors react to this," "will this move invite retaliation," "war-game this decision," or has a planned strategic move that needs competitor response forecasted from their actual incentive structure, not generic assumption.

This skill should be used when the user asks to "map the competitive landscape," "who are our real competitors," "find white space in this market," or needs competitors grouped by actual strategic logic rather than by surface product category.

This skill should be used when the user asks to "map the incentives here," "why is this player behaving this way," "predict how X will react," or has a strategic situation where a player's actual incentive structure — not their stated motivation — needs to be reasoned through.

This skill should be used when the user asks to "where's the information asymmetry here," "are we the informed or uninformed party," "how do we signal quality / screen for it," or has a negotiation, deal, or market situation where one party plausibly knows something the other doesn't.

This skill should be used when the user asks to "test our positioning," "are we differentiated," "is this a real strategy or just a slogan," or has a positioning statement that needs the trade-off discipline applied — what are you choosing not to do.

This skill should be used when the user asks to "cascade these OKRs," "break this down to team level," or has objectives/KRs at one level that need to flow down with a genuine contribution check, a capacity sanity check, and a check for goals that work against each other across teams.