Skip to content
Skills Library
Management & product · Analysis

dev-deep-dive

/dev-deep-dive

Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.

Repository
evo-nexus ↗
Licence
Apache-2.0
Last repository change
12.05.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.

Original author description

Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.

How it works

  1. Use When
  2. Workflow
  3. Pairs With
Original SKILL.md headings · 40 lines, 215 words
SKILL.md preview
---
name: dev-deep-dive
description: Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.
---

# Dev Deep Dive

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

A two-stage investigation that combines causal tracing with requirements crystallization. Use when both the cause AND the scope of a problem are ambiguous.

## Use When
- Production issue with unclear cause AND unclear scope of fix
- Bug report that needs both root cause analysis and clarification of "what does fixed look like?"
- Strategic problem where you don't know what to build OR why the current state isn't working

## Workflow

### Stage 1 — Causal trace
Hand off to `@trail-tracer`:
- Generate competing hypotheses
- Collect evidence FOR and AGAINST each
- Apply lenses (systems / premortem / science)
- Identify the discriminating probe
- Save report to `workspace/development/debug/[C]trace-{topic}-{date}.md`

### Stage 2 — Requirements crystallization
Hand off to `@echo-analyst` + `dev-deep-interview`:
- Surface unstated assumptions
- Define scope boundaries
- Identify missing acceptance criteria
- Save spec to `workspace/development/specs/[C]spec-{topic}-{date}.md`

### Stage 3 — Synthesis
- Combine the trace report and the requirements spec
- Output: a unified understanding of "what's broken AND what done looks like"
- Hand off to `@compass-planner` to plan the actual fix

## Pairs With
- `@trail-tracer` (Stage 1)
- `@echo-analyst` (Stage 2)
- `dev-deep-interview` (Stage 2)
- `@compass-planner` (Stage 3 handoff)

Versions

The database has no other skills named dev-deep-dive.

Database snapshot: 13.11.2026 · package version 69dbe5570b04 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90deep-dive
    2-stage pipeline: trace (causal investigation) then deep-interview (requirements). Activate when user says: deep dive, deep-dive, investigate deeply, trace and interview.
  • 100dev-deep-interview
    Socratic questioning to crystallize vague requirements into a testable spec. Use when input is ambiguous, when the user asks for "deep interview", or before dev-autopilot if the brief is too broad. Pairs with @echo-analyst.
  • 90dev-requirements
    AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user wants to capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2.
  • 100competitor-deep-dive
    Sourced deep dive on one competitor covering pricing, positioning, product, trust, legal, press, market activity, strengths, weaknesses. Use when "deep dive on a competitor", "research Northstar".
  • 90may-pm
    Use when product intent, user needs, scope, priorities or acceptance criteria are unclear, or stakeholder decisions conflict; not for a small fix with settled requirements.
  • 100research
    Research and investigation skills. Use for "research this", "investigate", "find out", and "deep dive".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.