deep-dive · akillness — Claude Code skill: trace causes, then define requirements
deep-dive — a two-stage skill: three parallel lanes trace why something broke, then a requirements interview starts from those findings. Built for bugs and changes in code you don't know yet.
no license 177 installs ★ 61 updated 2026-11-19
npx skills add akillness/jeo-skills --skill deep-dive -a claude-codeWhat deep-dive does
Deep Dive runs two stages back to back. The first digs into why something happens, splitting the work into three investigation lanes: a cause in the code, one in config or environment, and a mismatch between what is measured and what is assumed. The second stage converts what turned up into a spec through an interview.
Findings cross over at three injection points. The interview opens from a richer starting point, receives system context, and begins with the questions the trace could not settle on its own. State sits in the directory of whichever adapter is active (.omc/, .omx/, .agents/), and artifact paths are stored, so a run picks up again after the context gets compacted.
The skill does not execute anything itself; it hands the spec to the runtime's planner or executor. The handoff counts as ready once the saved files pass scripts/validate_deep_dive_artifacts.py. You confirm the lane hypotheses once at the start, and the trace then runs without interruption. Already know the root cause? Run /deep-interview on its own.
What it helps with
- trace a bug whose cause you can't pin down
- map how an existing subsystem behaves before changing it
- carry investigation findings into a spec instead of restarting the interview
- split a vague problem into three checkable hypotheses
- hand a finished spec to the runtime's planner
Example prompts for the agent
- Deep dive on the flaky password reset emails: find the cause first, then write up what we should change.
- Run deep-dive on the queue worker crash, then turn the findings into requirements.
- I want to know why the report export got slow before we plan any changes.
How to install deep-dive
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill deep-dive -a claude-code2Manually: put the files in place
~/.claude/skills/deep-dive/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/deep-dive/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill deep-dive -a codex2Manually: put the files in place
.agents/skills/deep-dive/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill deep-dive -a cursor2Manually: put the files in place
.cursor/skills/deep-dive/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills .agent-skills/deep-dive/SKILL.md2Manually: put the files in place
.github/skills/deep-dive/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill deep-dive -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/deep-diveManually: put the files in place
.devin/skills/deep-dive/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill deep-dive -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about deep-dive
How do I install deep-dive in Claude Code?
Run npx skills add akillness/jeo-skills --skill deep-dive -a claude-code. The skill lands at ~/.claude/skills/deep-dive/SKILL.md.
What does deep-dive do?
It chains a cause-tracing stage with a requirements interview, so the second stage starts from what the first one found rather than from scratch.
Does deep-dive need a particular runtime?
One adapter per run: OMC under Claude, OMX under Codex, OMA under Gemini/Antigravity. The trace and spec schema stays the same, while orchestration maps to whatever primitives the current tool actually has.
Similar skills
All skills for Agent setup: memory, context, orchestration →deep-dive by other authors comes first.