Skip to content
cccskills
FreePublished on GitHub

mece-analysis

Structure thinking using Mutually Exclusive, Collectively Exhaustive categories. Use when breaking down problems or ensuring complete coverage.

The English summary is being prepared. Showing the original description.

Works withFacebook
See how to install

Files included (2)

  • SKILL.md1.6 KB
  • agents/openai.yaml220 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

MECE Analysis

Structure thinking using Mutually Exclusive, Collectively Exhaustive categories.

When to Use

When you need to break down a problem, categorize options, or ensure complete coverage.

The Principle

MECE = Mutually Exclusive, Collectively Exhaustive

  • Mutually Exclusive: No overlap between categories
  • Collectively Exhaustive: All possibilities covered

The Process

1. Analyze Mutual Exclusivity

For each pair of items:

  • Is there any overlap?
  • Could something belong to both?
  • If overlap exists, redefine boundaries

2. Analyze Collective Exhaustiveness

For the whole set:

  • Are there gaps?
  • What scenarios aren't covered?
  • What's missing?

3. Create Logical Tree

Structure as hierarchy:

  • Top level: Broadest categories
  • Sub-levels: More specific breakdowns
  • Each level should be MECE

Example

Bad (not MECE):

  • Marketing channels: Social, Digital, Facebook, Email
  • (Facebook overlaps with Social and Digital)

Good (MECE):

  • Marketing channels: Paid, Owned, Earned
    • Paid: Social ads, Search ads, Display
    • Owned: Email, Website, App
    • Earned: PR, Reviews, Word of mouth

Output

  • MECE categories with clear boundaries
  • Logical tree showing hierarchy
  • Notes on any gaps or overlaps found

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os116Updated Oct 7, 2026

See all skills by itseffi

Report a problem with this skill