AugmentClaude

Consulting Writing

Structure writing for executives using pyramid, MECE, and bold-bullet frameworks.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/consulting-writing-alfadur7/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Management-consulting writing craft — McKinsey SCR (Situation·Complication·Resolution), Minto Pyramid/MECE, BCG bold-bullet executive summary, so-what upfront, numeric precision, Forrester Landscape. Use when writing or reviewing an executive summary for decision-makers or a roll-up/landscape overview, or when a conclusion-first compressed structure, MECE completeness, or bold-bullet summary is needed.

What this skill does

consulting-writing

Writing craft drawn from management-consulting deliverables — the executive-summary / pyramid structure that compresses a complex domain for decision-makers, and the MECE completeness of a roll-up. criteria.json is the SoT for each criterion's definition, comparator, and source; shared parsing for the deterministic checks is orchestrator-injected (the skill is content-type-agnostic). Examples are illustrative of the target English prose.

MECE completeness (con.mece-axes · con.mece-clusters)

A roll-up document must cover its subitems with no overlap and no gaps — the MECE principle separates a set of items into subsets that are "mutually exclusive (ME) and collectively exhaustive (CE)." Group many items under 2–4 top axes, place every item under at least one axis, and put anything that fits nowhere into an explicit residual (기타 / "other") axis. Every subunit (cluster, theme, …) must appear in the roll-up (collectively exhaustive — no subunit dropped).

Executive Summary structure (con.scr · con.so-what · con.bold-bullet · con.numeric-precision)

The intro craft that compresses a complex domain for a decision-maker. Resists deterministic measurement (judge=M, qualitative review); the source techniques shared by author and reviewer:

  • SCR (con.scr) — develop the intro as Situation → Complication → Resolution (McKinsey). e.g. ✅ "Market share fell 8% year over year (Situation). A competitor entered at a 15% lower price (Complication). We respond by repositioning as premium (Resolution)." / ❌ "The market environment is difficult and improvement is needed" (Situation·Complication·Resolution undifferentiated)
  • So-what upfront (con.so-what) — lead with the conclusion (the key implication), not a long description or preamble. e.g. ✅ "We can cut indirect costs by ₩2B per year — labor, supply waste, and process inefficiency are the drivers" (conclusion first) / ❌ "We analyzed three factors affecting profitability…" (description first)
  • Bold-bullet (con.bold-bullet) — build metric runs as a bold key-claim heading + supporting bullets, so the scannable takeaway is the bold line (BCG executive-summary standard: lead with the "so what", evidence below). e.g. ✅ "Market consolidation drives customer acquisition cost up 34% per year — Q2 three-way merger shrinks the vendor pool / pressure on the procurement team's volume discounts" (bold conclusion + grounds) / ❌ "The market is changing / competitors are consolidating / customers want better prices" (flat bullets, no conclusion)
  • Numeric precision (con.numeric-precision) — support claims with concrete numbers (amount·date·%·proper noun) instead of vague quantifiers. e.g. ✅ "Revenue grows 12% through Q3 2026, adding ₩4.5B" / ❌ "Revenue will rise significantly going forward" (abstract quantifier)
  • Numeric density (con.numeric-density) — do not overpack a paragraph with numbers; isolate key numbers in bold-bullets so they are not buried (deterministic measurement — per-paragraph number-token ceiling, threshold injected by manifest).

How each technique maps to a specific page/section is defined by the .claude/layers/ content-type guides.

Sources

Each URL points to the relevant page as of the last verification.

Related skills