mece-framework
/mece-framework
Porządkuje problemy, drzewa zagadnień, zestawy opcji, segmentacje, plany pracy, hipotezy i listy ryzyk według zasady MECE: bez nakładania i bez luk.
- Autor
- fzfclee ↗
- Repozytorium
- consulting-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 10.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Porządkuje problemy, drzewa zagadnień, zestawy opcji, segmentacje, plany pracy, hipotezy i listy ryzyk według zasady MECE: bez nakładania i bez luk.
Oryginalny opis (EN)
Use when a problem, issue tree, option set, segmentation, workplan, hypothesis set, risk list, or recommendation structure must be mutually exclusive and collectively exhaustive. Use when applying MECE, no-overlap/no-gap structuring, consulting issue decomposition, taxonomy cleanup, or structured problem solving.
Jak działa
- Method Notes
- Required Inputs
- When Not To Use
- Step-by-Step Execution
- Output Template
- Quality Gate
Podgląd SKILL.md
--- name: mece-framework description: Use when a problem, issue tree, option set, segmentation, workplan, hypothesis set, risk list, or recommendation structure must be mutually exclusive and collectively exhaustive. Use when applying MECE, no-overlap/no-gap structuring, consulting issue decomposition, taxonomy cleanup, or structured problem solving. license: Apache-2.0 --- # MECE Framework Use this skill to check and improve whether a structure is clear, non-overlapping, and complete enough for decision work. ## Method Notes - MECE means Mutually Exclusive and Collectively Exhaustive. - Mutually exclusive means categories do not overlap in a way that creates double counting or unclear ownership. - Collectively exhaustive means the structure covers all material parts of the question within the chosen scope. - MECE is a discipline, not a slogan. Use it to improve clarity, not to make every real-world situation artificially neat. ## Required Inputs Collect or infer these inputs before execution: - core question or decision - current structure, list, tree, segmentation, options, hypotheses, or workplan - scope boundary - intended use of the structure - known exclusions, constraints, or edge cases If an input is missing, do not block automatically. Mark it as `missing`, state the assumption used, and add a validation action. ## When Not To Use Do not use MECE when the user is still exploring raw ideas and premature structure would hide weak signals. Use `affinity-diagram` or `mind-map-analysis` first. ## Step-by-Step Execution | Step | Required input | How to execute | Output | |---|---|---|---| | State the scope | Core question, intended use, boundary. | Define what the structure must cover and what it deliberately excludes. | Scope statement. | | List current branches | Existing list, tree, segments, options, hypotheses, or actions. | Put all current items at the same logical level when possible. | Current structure. | | Test mutual exclusivity | Current branches, definitions. | Check whether two items overlap, duplicate, mix levels, or create ambiguous ownership. | Overlap diagnosis. | | Test collective exhaustiveness | Scope, edge cases, known exclusions. | Ask what important case, stakeholder, cause, option, segment, or risk is missing. | Gap diagnosis. | | Fix level and logic | Overlaps, gaps, mixed levels. | Rename, split, merge, move, or add branches so each item has one clear place. | Revised structure. | | Define inclusion rules | Revised structure. | Write a short rule for what belongs in each branch and what does not. | Category rules. | | Stress test with examples | Edge cases, sample facts, known scenarios. | Place sample items into the structure and check if any item fits nowhere or fits multiple places. | Stress-test result. | ## Output Template ```markdown ### 1. Scope - Core question: - Structure being tested: - In scope: - Out of scope: ### 2. Current Structure | Branch / item | Current definition | Level | Issue detected | |---|---|---|---| | | | same level / mixed level | overlap / gap / unclear / ok | ### 3. MECE Diagnosis | Problem | Where it appears | Why it matters | Fix | |---|---|---|---| | overlap / duplicate / mixed level / missing branch / unclear boundary | | | | ### 4. Revised MECE Structure | Branch | Inclusion rule | Exclusion rule | Example items | |---|---|---|---| | | | | | ### 5. Stress Test - Item that fits clearly: - Edge case: - Remaining ambiguity: - Next refinement: ``` ## Quality Gate - Do not confuse MECE with excessive completeness. The structure only needs to be complete for the current decision scope. - Keep items at the same logical level whenever possible. - Avoid mixing causes, symptoms, actions, owners, and metrics in the same branch set unless that is the deliberate design. - Define inclusion and exclusion rules for ambiguous branches. - If full MECE is impossible, state the practical boundary and remaining ambiguity.
Wersje
W bazie nie ma innych skilli o nazwie mece-framework.
Migawka bazy z 13.11.2026 · wersja paczki 9587ae6904c8 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100issue-tree-builder
Rozkłada złożone problemy na rozłączne i wyczerpujące składniki (MECE) w stylu drzewa zagadnień McKinsey z podejściem opartym na hipotezach, do planów pracy i przygotowania do case interview. - 100mece-analysis
Porządkuje problem w kategorie wzajemnie rozłączne i łącznie wyczerpujące (MECE), by rozbić zagadnienie i upewnić się, że niczego nie pominięto. - 100structured-problem-solving
Prowadzi przez strukturalne rozwiązywanie problemu biznesowego: zamknięta definicja, drzewo MECE, hipoteza do obalenia i plan analiz. - 100meta-structured-problem
Rozkłada złożony problem metodą MECE, drzew zagadnień, podejścia hipotezowego i zasady piramidy, by uporządkować analizę w stylu konsultingowym i rekomendacje. - 100issue-trees
Rozbija złożone problemy na wzajemnie wykluczające się i wyczerpujące gałęzie drzew zagadnień, przy rozwiązywaniu problemów, analizie przyczyn źródłowych i szukaniu rozwiązań w stylu konsultingowym. - 100issue-tree
Porządkuje niejasny problem w drzewo zagadnień MECE przed diagnozą, planowaniem lub decyzją, w trzech typach: Why (przyczyny), What (rozbicie dostarczanego rezultatu na pracę) i How (ranking działań).