Loading...
Loading...
Found 8 Skills
Conduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Investigates a question about a codebase or system and answers it from evidence, without changing anything. Gathers evidence first (git history and blame, CI run logs, tests, ADRs and docs), then uses Five Whys for 'why is X failing / why did X break', a scored placement analysis for 'where should Y live' (module, layer, script, package, CI job, or bounded context), and structured explanation, description, or a decision matrix for how/what/which questions. Checks the question's premise and says what evidence it could not reach. Use when the user says /ask-why, asks 'why is this failing', 'why did this break', 'what was the root cause', 'where does this belong', 'where should this check/code live', or wants a root cause explained for a bug that is already fixed. Read-only: no code is written or changed.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.