Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.
$npx -y skills add tkellogg/open-strix --skill five-whysInstalls into the current project.
Run `npx skills use "https://github.com/tkellogg/open-strix" --skill "tkellogg/open-strix/five-whys"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/tkellogg/open-strix" that are relevant to the current task. Run `npx skills add "https://github.com/tkellogg/open-strix"` and select the relevant skills, then follow their instructions.