---
name: Deep Dive
slug: deep-dive-3
category: AI Engineering
description: Deep Dive helps when requirements are incomplete or conflicting by running a structured interview, recording assumptions, and producing a launch brief. Use it before planning or implementation when scope or acceptance criteria are unclear.
github: "https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/deep-dive"
language: JavaScript
stars: 210
forks: 27
install: "npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/deep-dive ~/.claude/skills/deep-dive"
installs_to: ~/.claude/skills/deep-dive
source_path: skills/deep-dive/SKILL.md
collection_size: 11
category_size: 2970
collection_url: "https://dirskills.com/collections/Joonghyun-Lee-Frieren/oh-my-antigravity"
added: 2026-09-04T05:26:20.988Z
last_synced: 2026-09-04T05:26:20.988Z
canonical_url: "https://dirskills.com/skills/deep-dive-3"
---

# Deep Dive

Deep Dive helps when requirements are incomplete or conflicting by running a structured interview, recording assumptions, and producing a launch brief. Use it before planning or implementation when scope or acceptance criteria are unclear.

**Install:**

```bash
npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/deep-dive ~/.claude/skills/deep-dive
```

## README

## Purpose

Use this skill when requirements are incomplete, conflicting, or too vague to begin implementation safely.

## Trigger

- User asks for implementation but goals/constraints are still unclear
- Multiple interpretations exist for scope, acceptance criteria, or architecture direction
- Team needs a compact interview artifact before `/oma:team-plan` or `/oma:team-prd`

## Workflow

1. Trace known facts from the request and current repository context.
2. Compute a simple clarity score (`low`, `medium`, `high`) for implementation readiness.
3. Run a structured interview pass:
   - essential questions (must answer before planning)
   - standard questions (quality/cost/risk tuning)
   - deep questions (edge-case and long-term maintainability)
4. Record assumptions explicitly and mark each as validated, pending, or risky.
5. Produce a launch brief that can be consumed by planning/execution stages.
6. If filesystem tools are available, update:
   - `.omg/state/interview-context.json`
   - `.omg/state/launch-brief.md`

## Output Template

```markdown
## Clarity Score
- level: low|medium|high
- rationale: ...

## Known Facts
- ...

## Open Questions
1. ...
2. ...

## Assumption Ledger
| Assumption | Status (validated/pending/risky) | Validation Path |
| --- | --- | --- |
| ... | ... | ... |

## Launch Brief
- objective:
- boundaries:
- acceptance hints:
- recommended next command:
```

## Notes

- Keep output concise and operator-facing.
- Do not start coding when essential interview questions are unresolved.
- This skill remains extension-native (prompt/state level), without external daemons or runtime wrappers.