메뉴
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.
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 "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.
| name | allocate-resources |
| description | 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. |
| 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"} |
For CSO, portfolio managers, or strategy leads diagnosing whether capital, headcount, and management attention match stated strategic priority — not history, politics, or sunk cost.
INPUT NEEDED when data missing.assess-growth-vectors if available.| Input | If missing |
|---|---|
| Org + corporate-strategy profiles | Surface practice-setup or [PROVISIONAL] |
| Strategic priority ranking | Halt — get or confirm before comparing |
| Allocation data (capital, HC, attention) | Ask; mark partial/missing per row |
Defaults: generic portfolio units; three priority tiers; [PROVISIONAL] on all figures. User must provide dollars/headcount — never invented.
option-evaluation): High = all options scored against same priority framework, sourced; Medium = criteria explicit, some data partial; Low = priority or spend unknown — structured first pass only.[review] on each move; strategist and portfolio committee decide.SOURCING / ASSUMPTIONS / NUMBERS / CONFIDENCE / GATE — per trust-conventions
Portfolio scope, allocation types, review forum, time horizon, evidence pack. Read profile definitions for units, tiers, stickiness.
Capital/budget, headcount, management attention, priority ranking — status and source per row. Management attention: [user estimate — not verified] if unsourced. Figures from ~~bi analytics, ~~spreadsheet, or ~~crm connectors must carry [sourced: <connector>, <asset>, <as-of>] on the load-bearing digit.
Per unit: priority tier/rank alongside capital %, headcount %, attention. Tag [sourced] or INPUT NEEDED.
| Pattern | Flag when |
|---|---|
| Legacy overfunding | Low priority, disproportionate share |
| Under-resourced growth bet | Top-tier bet, bottom-quartile spend |
| Under-differentiated allocation | Flat spend despite wide priority spread |
Ask why for legacy overfunding — history is diagnosis, not justification.
Cross-check assess-growth-vectors if run; else flag partial check.
Specific from→to moves with rationale — not vague "rebalance toward growth."
GATE before board/portfolio-committee finals.
CONFIDENCE: [defensible recommendation | structured first pass]
SCOPE: [units]
REVIEW FORUM: [working | portfolio committee | board]
LOAD-BEARING ASSUMPTIONS: [...]
ALLOCATION VIEW:
| Unit | Priority | Capital % | Headcount % | Attention | Flag |
...
UNDER-DIFFERENTIATION CHECK: [...]
GROWTH BETS CHECK: [...]
RECOMMENDED REALLOCATION:
| From | To | Type | Magnitude | Rationale |
...
STICKINESS NOTE: [...]
EVIDENCE GAPS: [...]
Input: Unit A priority tier 3 (exit candidate), 28% capital share; Unit B tier 1 adjacent bet, 8% capital.
Excerpt: Unit A flagged legacy overfunding; Unit B under-resourced growth bet. Reallocation: A −10% capital → B +10% [review] — adjacent bet cannot scale at current funding.
[PROVISIONAL]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. Branches: supply missing data, portfolio committee memo, exit-or-double-down on legacy units, assess-growth-vectors, or set reallocation trigger date.