Skip to content
cccskills
FreePublished on GitHub

root-cause-analysis

Uncover root causes through recursive Why questioning and consequence exploration. Use before acting on problems.

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

See how to install

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

Root Cause Analysis

Uncover root causes and explore consequences through structured questioning.

When to Use

When you need to deeply understand a problem, decision, or situation before acting.

The Process

1. Recursive "Why" Questioning

Start with the initial question and ask "Why?" repeatedly:

  • Ask "Why?" at least 5 times
  • Go deeper until you reach fundamental causes
  • If multiple reasons emerge, explore each branch

Example:

  • Why did users churn? → Onboarding was confusing
  • Why was it confusing? → Too many steps
  • Why too many steps? → We added features without simplifying
  • Why didn't we simplify? → No ownership of onboarding experience
  • Why no ownership? → Org structure doesn't align to user journey

2. Consequence Exploration

After finding root causes, explore forward:

  • 1st order: Immediate consequences
  • 2nd order: What results from those?
  • 3rd-5th order: Downstream effects

Consider both positive and negative outcomes.

3. First Principles Check

  • What fundamental truths underlie this?
  • What assumptions are we making?
  • What alternative perspectives exist?
  • Where are the gaps in logic?

Output Format

  • Root causes (the "Why?" chain)
  • Consequences (1st through 5th order)
  • First principles (fundamental truths, assumptions)
  • Conclusion (key insights)

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