dive

Trace system causes and interview requirements to generate a specification.

2|1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/yy1588133/oh-my-snow --skill dive-yy1588133
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dive
Source: https://github.com/yy1588133/oh-my-snow/tree/main/assets/skills/oms/dive
Command: npx skills add https://github.com/yy1588133/oh-my-snow --skill dive-yy1588133

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oms/trace, oms/interview, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users understand complex system behaviors and define clear specifications by guiding them through a structured two-phase process of tracing causes and interviewing requirements.

Core Features & Use Cases

  • Parallel Tracing: Conducts parallel trace investigations to uncover root causes and map system areas.
  • Interview with 3-Point Injection: Uses trace findings to inform an interview, avoiding redundant exploration and focusing on unresolved issues.
  • Spec Generation: Generates a comprehensive specification document based on trace findings and interview outcomes.
  • Use Case: When dealing with a complex issue, such as a system bug or a feature request, the Dive skill can help in understanding the root cause and defining a clear path for implementation.

Quick Start

Run the 'dive' command to initiate a deep dive investigation into a system issue.

Frequently Asked Questions about dive

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

FAQPage Schema
What is root cause analysis for system behavior and when do I need a specification?

Root cause analysis for system behavior traces complex issues to their origins, and you need specification generation when defining clear implementation paths for bugs or features. This process maps system areas and interviews requirements to produce comprehensive documentation.

How do I conduct a trace investigation and interview for system requirements?

You conduct trace investigation and requirement interviews by running a two-phase process. First, perform parallel tracing to map system areas, then use 3-point injection to feed trace findings into the interview, avoiding redundant exploration and focusing on unresolved issues.

Can I generate a specification document from trace findings and interview data?

Yes, you can generate a specification document from trace findings and interview data. The process integrates parallel trace investigation results with 3-point injection interview outcomes to automatically produce a comprehensive specification defining clear system behavior.

Do I need oms/trace and oms/interview skills to run a deep dive investigation?

Yes, you need the oms/trace and oms/interview skills to execute a deep dive investigation. These dependencies are required for conducting the parallel tracing and 3-point injection interview phases that generate the final specification.

What is the best way to investigate a complex system bug and define an implementation path?

The best way to investigate a complex system bug is using a structured two-phase deep dive process. It conducts parallel tracing to uncover root causes, then interviews requirements with 3-point injection to define a clear specification and implementation path.

Can I integrate system analysis and specification generation with other workflow tools?

Yes, you can integrate system analysis and specification generation with other tools. The deep dive process supports integration with other system analysis and specification skills to extend the workflow beyond the core trace and interview phases.