AI Agent Hub
Back to skills
McKinsey MECE Structured Writing icon

McKinsey MECE Structured Writing

Content Creation Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_8d4ddd46/mece into your AI assistant using https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Multi-point answers often become flat lists: the conclusion appears late, groups overlap, and hierarchy lacks order. McKinsey MECE Structured Writing is intended for reports, proposals, recommendations, and synthesis tasks, turning conclusion-first, top-down, MECE, and progressive logic into enforceable constraints.

How It Works

The skill first checks whether it should trigger. Simple facts, single-step operations, pure retrieval, or one-line requests are answered directly. When two or more logically connected points are required, it runs a three-step process: identify the problem type, select a construction path, and self-check the output. Core capabilities include SCQA framing, decomposition for root-cause, decision, workflow, and quantitative problems, induction or deduction ordering, and a problem → solution → validation chain for each dimension. It also checks for common anti-patterns: disconnected parent-child points, mixed classification criteria, mixed deduction and induction, and key sentences that are labels rather than claims.

Boundaries

It fits structured analysis better than pure narrative, casual chat, or single-sentence answers. If the result has three or more nested levels but only one core conclusion, more groups than needed, or a longer SCQA introduction than the body, the skill requires simplifying the output so the framework does not become redundancy.

Use Cases

  • When writing quarterly business reviews, organize revenue, cost, risk, and actions into a conclusion-first report and check whether groups are MECE.
  • When drafting a project proposal, structure recommendations as problem, cause, countermeasure, and validation to avoid mixing symptoms and root causes.
  • When summarizing competitor research, use SCQA to explain context, complication, question, and answer before making a go or no-go recommendation.
  • When emailing executives, state the optimization result first, list three supporting points, and keep it to one short paragraph.

Best For

  • Operations owners who write quarterly reviews and strategy notes, needing scattered data shaped into conclusion-first reports.
  • Strategy consultants who draft market-entry proposals and need to check problem types and MECE groupings.
  • Analysts who build competitor research or investment memos and need an SCQA intro with decision implications.
  • Product managers who report optimization or cost-governance results and need results, causes, actions, and validation.