When to use: You need a decision memo, not a brain dump — pyramid principle, MECE buckets, exec summary on top.
Flow
-
Trigger the consulting skill
Using the mckinsey-consultant skill, draft a memo: 'Should we acquire company X?' Inputs: our top 3 goals, company X data, risks.✓ Copied
→ Output leads with the recommendation, then supporting buckets (MECE), then evidence
-
Iterate
Tighten the bucket headers so each one is a full sentence argument.✓ Copied
→ Pyramid-style, each level of the argument summarized by its parent
Outcome: A memo your CEO can read in 90 seconds and drill into.
Pitfalls
- Skipping the synthesis and going straight to bullet lists — Force the recommendation onto the first line; bullets come after, never above the take
When to use: You want output that doesn't sound like default Claude.
Flow
-
Activate the writing pack
Use mimeng-writing: turn this rough draft into a long-form post about product market fit.✓ Copied
→ Voice is consistent, sentences are varied, no AI tells
-
Calibrate
Tune more toward conversational, less toward listicle.✓ Copied
→ Narrative flow increases; fewer headings
Outcome: Long-form content that sounds like you, not a bot.
Pitfalls
- Using the voice pack for topics it was never trained on — Be explicit about scope; fall back to generic writing for off-topic content
When to use: You want a structured, updatable analysis doc for a policy or market dataset.
Prerequisites
- Source dataset URL — Provide a data.gov / agency URL
Flow
-
Pick the tracker template
Use us-gov-shutdown-tracker as a template; adapt to <your dataset>.✓ Copied
→ Framework preserved: summary, key metrics, trend, sources
-
Fill with current data
Fetch the latest CSV, populate the sections, cite sources.✓ Copied
→ Numbers + source URLs for each claim
Outcome: A repeatable data-tracking doc.