deep-dive

To investigate intermittent production bugs and generate a requirements specification, provide a concise problem statement to trigger a 3-lane causal trace, followed by an interactive interview that crystallizes evidence-backed findings into a handoff-ready spec file.

Analyzing brownfield system impact and documenting requirements is best handled by running parallel causal tracing to uncover root causes, then synthesizing codebase context and critical unknowns into an actionable specification for downstream planning.

You can resume an interrupted root-cause analysis session because the pipeline features artifact persistence and state saving, allowing you to pause and continue the causal trace and interactive interview without losing progress.

To turn ambiguous feature exploration findings into actionable specs, the tool injects trace synthesis and per-lane critical unknowns into a stateful interview, directly translating investigative evidence into crystallized requirements.

The generated requirements specification works directly with autonomous execution tools by acting as an execution bridge, handing off the persisted spec files to downstream planners like omc-plan, autopilot, ralph, or team for immediate execution.