메뉴
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.
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 | deck-outline |
| description | 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. |
| allowed-tools | Read, Grep, Glob |
| metadata | {"version":"0.3.0","owner":"consulting practice","review_cadence":"quarterly","work_shape":"narrative-synthesis","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"} |
For consultants building a storyline-first, action-titled deck outline before slide design. Markdown outline only — hand off to presentation tools after approval.
narrative-builder if needed.| Input | If missing |
|---|---|
| Practice profile (slide title style, exhibits) | Proceed with action titles default; flag practice-setup |
| Governing thought / narrative | Ask to run narrative-builder first |
Thin narrative: label structured first pass; flag slides that don't trace to key line.
narrative-synthesis): High = every slide traces to key line; Medium = some exhibit TBD; Low = topic list without governing thought — flag.Full rules: ../../references/trust-conventions.md.
narrative-builder output if available; else ask to build narrative first.minto-pyramid.md — cut non-load-bearing slides.GOVERNING THOUGHT: [headline]
Slide 1 — [Action title]
Exhibit: [...]
Slide 2 — [Action title for key line point 1]
Exhibit: [...]
...
Flag slides that don't trace to a key line point.
Input: Governing thought: "Mid-tier price increase destroyed volume — revert pricing." Three MECE key lines.
Excerpt: Slide 1 action title states governing thought; Slides 2–4 map one key line each with exhibit notes (cohort chart, elasticity model, competitor scan).
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/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.
Follows plugin CLAUDE.md § Outputs. Next: approve outline → build slides, or /consulting:so-what-sharpener on weak titles.