Loading...
Loading...
Found 168 Skills
Comprehensive A3 one-page problem analysis with root cause and action plan
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.
Calculate and diagnose Overall Equipment Effectiveness (OEE) by decomposing into Availability, Performance, and Quality rates. Use this skill when the user needs to measure production line efficiency, identify equipment losses, benchmark manufacturing performance, or justify capital investment — even if they say 'why is our output low', 'machine utilization report', 'production efficiency', or 'how much capacity are we losing'.
Follow this sub-process when fixing bugs—turn the verbal description of "discovered a problem" into a closed loop of verification and repair, leaving three documents in the middle: issue report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code", avoiding several common pitfalls: the problem description in your mind disappears after modification, fixing only the surface without analyzing the root cause, uncontrollable expansion of repair scope that cannot be traced, and not knowing if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing outputs. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only keeping the fix-note.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Systematic Fishbone analysis exploring problem causes across six categories
CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.
Comprehensive debugging methodology for finding and fixing bugs (formerly debugging). This skill should be used when debugging code, investigating errors, troubleshooting issues, performing root cause analysis, or responding to incidents. Covers systematic reproduction, hypothesis-driven investigation, and root cause analysis techniques. Use when encountering exceptions, stack traces, crashes, segfaults, undefined behavior, or when bug reports need investigation.
Root cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected.
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res
Investigate and diagnose issues without necessarily fixing them