メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | build-vs-buy-vs-partner |
| description | 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. |
| allowed-tools | Read, Grep, Glob |
| metadata | {"version":"0.3.0","owner":"corporate-strategy practice","review_cadence":"quarterly","work_shape":"option-evaluation","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"} |
When a capability gap needs build/buy/partner framing — forces each path's known failure pattern into the conversation, not cost comparison alone.
synergy-stress-test.| Input | If missing |
|---|---|
| Capability gap stated precisely | Ask before evaluating paths |
| Strategic priority link | Question whether gap worth closing |
Missing build track record: note haircut cannot be calibrated — [review].
synergy-stress-test.CAPABILITY GAP: [...]
CORE OR COMMODITY: [...]
BUILD: [...] — Failure pattern risk: [...]
BUY: [...] — [synergy-stress-test if live]
PARTNER: [...] — Exit mechanism: [...]
RECOMMENDATION: [build | buy | partner] — [failure pattern + mitigation]
Input: Need ML fraud model. Team has no ML delivery track record.
Excerpt: Commodity-adjacent capability; BUILD failure pattern high (overrun history); PARTNER exit mechanism missing — flag. Recommend partner with defined exit or buy [review].
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/corporate-strategy/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /corporate-strategy:practice-setup auto-applies a full profile write.
Follows plugin CLAUDE.md § Outputs. Next: synergy-stress-test, evaluate-strategic-option, or implementation planning.