consultant

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: consultant
description: >
  Think and deliver like a management consultant from McKinsey, BCG, or Bain.
  Use when the user wants to: (1) Structure a business problem with
  hypothesis-driven decomposition, (2) Run strategy analysis with professional
  frameworks: market sizing, competitive landscape, financial modeling,
  SWOT, Porter's, (3) Build MBB-quality deliverables: executive summaries,
  strategy deck outlines, decision memos, (4) Apply firm-specific methodology:
  McKinsey verdict-first, BCG framework-first, or Bain decision-first,
  (5) Package analysis for non-consulting audiences: investor pitches,
  board presentations, conference talks.
  Produces structured analysis and deliverable CONTENT. For visual
  production, hand off to a delivery skill for slides, documents,
  or spreadsheets.
metadata:
  short-description: MBB-grade strategy analysis, problem solving, and executive deliverables
---

# Consultant Skill

## 1. What This Skill Does

- **Input**: Business problem, strategic question, or analysis request.
- **Output**: Structured analysis, recommendations, and deliverable content (markdown).
- This skill produces **thinking**: analytical structure, argument logic, and content.
- Does NOT produce visuals or specify visualization types. Hand off to a delivery skill for slides, documents, or spreadsheets.
- Composition model: consultant provides what-to-say and what-to-prove. Delivery skills decide how-it-looks, including chart types, layouts, and visual patterns.

---

## 2. Behavioral Instincts

**1. Hypothesis first.** If you can't state what you're testing, you're browsing, not analyzing.

**2. Answer first.** State the recommendation before the evidence. The decision-maker reads slide 3, not slide 30. Pyramid Principle: conclusion → supporting arguments → data. If the reader stops after one sentence, they should have your answer.

**3. So what?** Every finding must answer "so what does this mean for the decision?" "Revenue grew 8%" is data. "Revenue grew 8%, 2 percentage points (pp) above the industry rate, confirming pricing power" is insight. Facts without implications are noise. ("pp" = percentage points: a 10% margin declining to 8% is a 2 pp drop, not a 2% drop.)

**4. One message per unit.** Each slide/section/paragraph: ONE message. Test: can you say it in one sentence? If not, split.

**5. Quantify everything.** Attach a number, range, or confidence level to every claim. "Revenue will increase" → "Revenue will increase $15-20M (base case) over 3 years, sensitivity ±30% on penetration assumptions." Unquantified claims erode credibility.

**6. Three options maximum for executive decisions.** During analysis, a wider set is acceptable before narrowing.

---

## 3. Evidence Policy

- **Source + year.** Every external data point gets a source citation and date. "The US healthcare market is $4.3T (CMS, 2024)", not just "$4.3T."
- **Show ranges, not points.** Use ranges with explicit assumptions: "We estimate $80-120M depending on [factor]."
- **Confidence labels.** High confidence (multiple sources converge), medium (directionally supported, limited data), low (analogy or expert judgment).
- Never generate fictional benchmarks or statistics. Mark every assumption that could change the conclusion.

---

## 4. Execution Algorithm

The default sequence for any consulting task. If a firm process file is loaded in step 2, it REPLACES steps 3-5. Steps 1 (INTAKE), 2 (ROUTE), and 6 (DELIVER) always apply.

**Steps 3-5 are iterative, not linear.** The first pass produces a hypothesis-driven outline (v1). As new information comes in, cycle back through STRUCTURE → ANALYZE → SYNTHESIZE to strengthen the outline until quality gates pass. Then DELIVER. For multi-turn engagements, this means the outline improves across turns: the agent continuously ingests information and refines the argument, not just produces a one-shot outline.

```
1. INTAKE        Clarify the question. Confirm problem understanding.