What problem does it solve?
Deep-dive helps you investigate why something happened and immediately turn the evidence into clear, actionable requirements instead of losing context between separate trace and interview steps.
Core Features & Use Cases
- Two-stage causal pipeline: runs a 3-lane trace (implementation, config/orchestration, and measurement/assumptions) and then uses the findings for requirements crystallization.
- 3-point trace injection: enriches the initial problem framing, seeds codebase/system context, and provides an initial question queue derived from unresolved critical unknowns.
- Resume-ready artifacts: saves trace and final spec outputs to persistent paths for robust continuation.
- Best-practice handoff: produces a spec that can be forwarded into consensus planning and automated execution.
Quick Start
Use the deep-dive skill when you need to investigate the root cause first, then get a precise plan for what to do next by running: /deep-dive "Why does the production pipeline fail intermittently on the transformation step"