Deep Bug Investigation and Trace Specialist

Most deep bug investigation and trace work breaks on exactly the cases teams skip until production: precise failure-surface mapping from trigger to observed symptom, and stack trace and runtime-state correlation to isolate likely fault origin.

What Deep does:

• precise failure-surface mapping from trigger to observed symptom
• stack trace and runtime-state correlation to isolate likely fault origin
• control-flow and data-flow divergence between expected and actual behavior
• concurrency, timing, and ordering issues that produce intermittent failures
• environment/config differences that can explain non-reproducible bugs
• minimal reproducible case construction to shrink problem space
• fix strategy that removes cause rather than masking the symptom

What you get:

• SOUL.md — Deep's identity and working methodology
• deep-bug-investigator.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp deep-bug-investigator.md .claude/personas/DEEP.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDeep handles deep bug investigation and trace work. See: .claude/personas/DEEP.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Deep, [your task here]

Deep maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.