deep-dive

Coordinate trace-driven investigation and structured interviews to crystallize requirements into actionable specs.

6|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ImL1s/flutter-claude-skills --skill deep-dive-iml1s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-dive
Source: https://github.com/ImL1s/flutter-claude-skills/tree/main/skills/deep-dive
Command: npx skills add https://github.com/ImL1s/flutter-claude-skills --skill deep-dive-iml1s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Dive orchestrates a 2-stage workflow that first investigates WHY something happened (trace) and then crystallizes WHAT to do (deep-interview) using a 3-point injection to seed initialization with trace findings. The result is a crystal-clear spec grounded in evidence, not assumptions.

Core Features & Use Cases

  • Parallel trace lanes: runs three hypotheses in parallel to map root causes and gather evidence for and against each lane.
  • 3-point injection: injects trace findings into the interview initialization to seed questions and focus the crystallization process.
  • Stateful orchestration: persists across phases so that context can be resumed after interruptions, and enables downstream execution bridging.
  • End-to-end workflow: outputs a deep-dive spec that feeds into omc-plan and autopilot for automated execution in downstream pipelines.

Quick Start

Run the /deep-dive command with your initial problem description to begin the trace-and-interview workflow.

Frequently Asked Questions about deep-dive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I crystallize ambiguous requirements into actionable specs for greenfield or brownfield projects?

Crystallize ambiguous requirements by running a trace-driven investigation to find root causes, followed by a structured interview. This 2-stage workflow maps evidence and injects findings into the interview phase to produce a clear, grounded spec.

What is the best way to investigate root causes when facing an ambiguous software engineering problem?

Investigate root causes by running parallel trace lanes that explore three hypotheses simultaneously. This approach gathers evidence for and against each lane, ensuring the final analysis is grounded in facts rather than assumptions.

How does state persistence work during a trace and interview workflow?

State persistence saves context across phases so you can resume the workflow after interruptions. It maintains the trace findings and interview progress, enabling seamless continuation and bridging to downstream execution pipelines.

Can I feed the output spec directly into automated planning and execution pipelines?

Yes, the output spec feeds directly into downstream planning and automation tools like omc-plan and autopilot. The workflow bridges to these pipelines, enabling automated execution of the crystallized requirements.

Does deep-dive work for both new and existing software projects?

Yes, it is designed for both greenfield and brownfield projects. It applies trace-driven investigation and structured interviews to ambiguous problems in any project context to guide teams from root cause to actionable specs.