菜单
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.
用 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 | narrative-builder |
| description | 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. |
| 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"} |
Turn raw input into Minto pyramid: governing thought, 3–5 MECE key line points, support bullets. See ../../references/minto-pyramid.md.
deck-outline / exec-memo.| Input | If missing |
|---|---|
| Raw findings/notes | Ask user to provide |
| Reader's real question | Ask before structuring |
| Practice profile | Default inductive; flag practice-setup |
Thin input: governing thought flagged [review]; Known gaps section required.
trust-conventions.md.GOVERNING THOUGHT: [...]
1. [Key line point 1]
- [Support]
2. [...]
Grouping logic: [deductive | inductive] — [rationale]
Known gaps / flags: [...]
Input: Interview notes on pricing. Question: should we revert mid-tier increase?
Excerpt: Governing thought answers revert yes; three MECE key lines; gap flagged: no competitor primary research.
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: /consulting:deck-outline or /consulting:exec-memo.