dev-deep-dive

Trace causal signals and crystallize requirements for ambiguous engineering problems.

520|175|Updated Apr 8, 2026

Search Tags:#debugging #root cause analysis #specification #requirements #systems thinking #incident response

Ready to run

npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deep-dive-evolution-foundation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-deep-dive
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-deep-dive
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deep-dive-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you resolve production or engineering issues when you don’t know both the cause and the real scope of the required fix.

Core Features & Use Cases

Two-stage investigation: first traces causal signals to generate and discriminate between hypotheses, then crystallizes requirements into clear boundaries and acceptance criteria.
Artifacts for execution: saves a trace report and a requirements spec to workspace paths for later planning and implementation.
Use Case: when monitoring alerts or a bug report arrives with symptoms but ambiguous root cause, it produces a unified understanding of what is broken and what “done” looks like so planning can proceed.

Quick Start

Use the dev-deep-dive skill when you face an unclear production issue and ask it to produce a causal trace and a requirements spec to define the scope of a correct fix.

Frequently Asked Questions about dev-deep-dive

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

FAQPage Schema

How do I find the root cause of an ambiguous production incident?▼

To find the root cause of an ambiguous production incident, you need causal tracing to generate and discriminate between hypotheses using available signals. This process clarifies what is broken before defining any solution scope.

What is the best way to define requirements for a bug fix with unclear boundaries?▼

Defining requirements for a bug fix with unclear boundaries requires requirements crystallization to establish clear solution scope and acceptance criteria. This ensures planning proceeds with a unified understanding of what done looks like.

When do I need causal tracing and requirements crystallization for engineering problems?▼

You need causal tracing and requirements crystallization when facing engineering problems where neither the underlying cause nor the required build is well understood. This applies to ambiguous bug reports, monitoring alerts, and strategic initiatives.

How do I turn a vague bug report into a scope-ready specification?▼

To turn a vague bug report into a scope-ready specification, run a two-stage investigation that first traces causal signals and then crystallizes requirements into clear boundaries. The resulting specification is saved to your workspace for implementation planning.

Can I use this approach for strategic initiatives with unclear build requirements?▼

Yes, you can use this approach for strategic initiatives with unclear build requirements. It resolves ambiguity by applying systems thinking to produce discriminating evidence reports and scope-ready specifications for downstream planning.

What limitations exist when debugging production issues with ambiguous symptoms?▼

When debugging production issues with ambiguous symptoms, the limitation is that you must have sufficient causal signals available to discriminate between hypotheses. Without traceable monitoring data, generating a definitive root cause report is constrained.