Trace root causes and interview to define actionable requirements.
npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill deep-dive-jmstar85
Please help me install this Agent Skill. Skill: deep-dive Source: https://github.com/jmstar85/oh-my-githubcopilot/tree/main/.github/skills/deep-dive Command: npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill deep-dive-jmstar85
Orchestrates a two-stage trace-and-interview workflow to identify root causes and translate findings into actionable requirements.
Provide a problem statement and the desired outcome to initiate a two-stage trace-and-interview investigation.
High-intent search queries and answers about installing and using this skill.
To investigate an unknown software bug root cause, you can use a two-stage trace-and-interview pipeline. It traces root causes and conducts structured interviews to inject findings into prompts, yielding concrete actionable execution requirements.
A trace-to-interview workflow is a multi-agent pipeline guiding software engineering investigations through phases like Initialize, Lane Confirmation, Trace Execution, and Interview with Trace Injection to define actionable requirements.
Yes, you can use execution agents like omg-autopilot or ralph after a root cause investigation. The pipeline includes an Execution Bridge phase designed to support integration with these agents for downstream execution planning.
Trace findings and structured interview outputs are stored under the .omg/specs directory. This output preservation ensures investigation data remains accessible for audit and downstream execution planning.
To start a feature exploration or performance review with an unknown root cause, provide a problem statement and the desired outcome. This input initiates the two-stage trace-and-interview investigation pipeline.
HyperionBurnDetermine an unknown failure's root cause via a trace-and-interview workflow.
HyperionBurnRead JSON state files to report active OMG execution modes and progress.
Hyeonjun0527Trace root causes and crystallize requirements via a 2-stage interview process.
VertaKhanGuides root-cause debugging through four phases: investigate, analyze, hypothesize, implement.
