- Home
- Skills
- Fleurytian
- Awesome Claude Skills
- Mckinsey Consultant 11
mckinsey-consultant-11_skill
- Python
168
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill fleurytian/awesome-claude-skills --skill mckinsey-consultant-11- LICENSE1.0 KB
- README.md1.2 KB
- SKILL.md18.1 KB
Overview
This skill replicates a McKinsey-style problem solving system to produce structured business analyses and slide decks. It combines hypothesis-driven issue trees, MECE decomposition, Dummy Page design and automated per-page data collection to generate professional PPT and Excel deliverables. The architecture uses progressive disclosure and dependency-aware page sequencing to support cross-conversation continuation and efficient context usage. It is optimized for iterative, stepwise work so large projects stay stable and traceable.
How this skill works
Start by defining the problem boundary and desired output, then build an Issue Tree and hypotheses to drive research. The system designs Dummy Pages with explicit page dependency annotations and generates each page in a strict loop: check dependencies, search, record source URLs, populate Excel, build the slide, self-check and pause for confirmation. Only required reference modules are loaded on demand (methodology, layouts, Excel spec, etc.), and per-page contexts are cleared after completion to minimize memory usage.
When to use it
- When you need a hypothesis-driven, MECE-structured analysis and executive slides
- For multi-page slide decks that require reliable cross-session continuation
- When you want traceable data sources and reproducible Excel artifacts per slide
- For projects where staged delivery and explicit page dependencies reduce rework
- When you prefer an iterative per-page workflow instead of all-at-once generation
Best practices
- Provide a clear core question and confirm 'start' before entering the full workflow
- Accept the Dummy Pages output early to lock layouts and dependency order
- Generate independent pages first, then front-dependent pages, and leave the executive summary last
- Upload any existing Dummy.md, PPT or Excel to resume across conversations
- Respond to per-page confirmations to keep the workflow controlled and auditable
Example use cases
- Build a 15–25 page go-to-market analysis with linked Excel data and source URLs
- Resume a paused project by uploading the Dummy Pages file and continuing from a specific page
- Generate hypothesis-led competitor and market analyses with MECE issue trees
- Produce an executive summary at the end once all analysis pages are complete
- Create repeatable slide templates and Excel sheets conforming to design and data specs
FAQ
Upload the project Dummy Pages (and any PPT/Excel). The skill reads the Dummy, identifies page status and dependency types, then continues from the specified page using on-demand loading of specs.
Can it produce Word reports as well as PPT?
Yes—Word output is optional and generated only when explicitly requested, triggering the delivery summary specifications.