Generate ranked hypotheses and track root cause analysis in a living investigation document.
npx skills add https://github.com/Kibbey/fyli --skill investigator
Please help me install this Agent Skill. Skill: investigator Source: https://github.com/Kibbey/fyli/tree/main/.claude/skills/investigator Command: npx skills add https://github.com/Kibbey/fyli --skill investigator
This skill enables teams to perform structured, hypothesis-driven root cause analysis by generating ranked hypotheses and maintaining a living investigation document that records hypotheses, tests, findings, and resolution status.
Create an investigation by defining the problem and creating an investigation document, then let the skill propose hypotheses and prompt you to pick one to test.
High-intent search queries and answers about installing and using this skill.
Structured root-cause analysis automates hypothesis-driven investigation by generating ranked causes with test plans. It maintains a living investigation document to track tests, findings, and resolution status across the debugging lifecycle.
Hypothesis-driven investigation generates prioritized plausible causes with rationale and test plans. You interactively select which hypothesis to test first, and results are documented automatically in a markdown file under docs/investigations.
To start an investigation, define the problem statement to create an investigation document. The workflow then proposes hypotheses and prompts you to select one to test, tracking progress through problem definition, testing, and resolution phases.
Yes, hypothesis-driven root cause analysis applies to incident reviews and complex problem-solving tasks. It provides structured hypothesis testing and traceable documentation to guide you from problem definition through to resolution.
Investigation documents are stored as markdown files at docs/investigations/YYYY-MM-DD-<slug>.md. This living document automatically records problem statements, tests, findings, and progress throughout the investigation lifecycle.
No dependencies or components are required to run an investigation. The workflow uses the AskUserQuestion tool to interactively select hypotheses and automatically stores progress in markdown format.
unblockedGenerate ranked hypotheses and parallel investigation tracks in INCIDENT format.
ChazzCoinManage cross-stack incident lifecycles with markdown and filesystem operations.
ibnuhalimmReproduce and solve bugs through structured phases and root-cause analysis.
bugrabilgeGuide hypothesis-driven debugging through a 4-phase process using observability tools.
