メニュー
MECE (Mutually Exclusive, Collectively Exhaustive): the McKinsey structuring principle.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Canonical b00t reviewer capability — adversarial multi-framework code/datum review. Shared across all harnesses (Claude Code, opencode, Hermes, b00t-cli). Loaded via: b00t learn reviewer, or by harness-specific role supplements.
Remove AI-generated artifacts from code. Three-phase certainty-graded cleanup. Use after any AI implementation session or before PR creation.
8-phase agile workflow — strategy→ideate→brainstorm→plan→work→review→compound→pulse. State machine with FOL-guarded transitions, gh-issues backlog, executable just harness. Inspired by everyinc/compound-engineering-plugin.
Australian crypto tax treatment per ATO guidance QC 53725. Crypto assets are CGT assets under ITAA 1997 s 108-5. Each disposal triggers CGT event A1. Covers personal-use exception, trading stock test, and the 50% CGT discount.
Australian R&D Tax Incentive (RDTI) — ITAA 1997 Division 355. Covers eligibility criteria for core and supporting R&D activities, registration with AusIndustry/IP Australia, expenditure categories, offset rates, and the company size threshold test.
Evidence graph construction for tax audit trails. Each Satisfies check emits EvidenceNode structs with Blake3 content hashes. Evidence chains are tamper-evident and link legislative citations to factual findings.
| name | mece |
| type | skill |
| hint | Mutually Exclusive Collectively Exhaustive — structure thinking so nothing overlaps or is missed |
| version | 1.0.0 |
| tags | ["transferable","mece","structure","exhaustive","exclusive","taxonomy","categorize","framework"] |
| tier | sm0l |
| complexity | 3 |
| description | MECE (Mutually Exclusive, Collectively Exhaustive): the McKinsey structuring principle. |
MECE stands for Mutually Exclusive, Collectively Exhaustive — the McKinsey structuring principle. Mutually Exclusive means no item belongs to two categories; overlaps equal ambiguity and missed edge cases. Collectively Exhaustive means all possibilities are covered; gaps equal hidden assumptions. Before solving a problem, structure the problem space: draw the tree and check each node.
Test mutual exclusivity: "can this item appear in two branches?" If yes, redefine the branches. Test collective exhaustiveness: "is there anything not captured?" If yes, add a branch or expand scope. In code, MECE applies to enum variants, error types, match arms, and API routes. In reasoning, it applies to hypothesis lists, root cause categories, and option sets.
Apply MECE when structuring a problem space, designing a taxonomy, writing match arms, defining error types, or enumerating hypotheses. Use it whenever completeness and non-overlap matter.
