Trace causes and crystallize requirements for ambiguous production incidents.
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-deep-dive
Please help me install this Agent Skill. Skill: dev-deep-dive Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-deep-dive Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-deep-dive
Two-stage investigation combines causal tracing with requirements crystallization to resolve problems where the cause and the scope are unclear.
Initiate a two-stage investigation by performing causal tracing followed by requirements crystallization when both the cause and the scope of a problem are unclear.
High-intent search queries and answers about installing and using this skill.
Two-stage investigation is a method that combines causal tracing to generate competing hypotheses with requirements crystallization to clarify scope for ambiguous issues. It enforces a structured workflow that concludes with synthesized handoffs to planners for production incidents and cross-team problems.
Conduct a causal trace by generating competing hypotheses, collecting evidence, and applying analytical lenses to the production incident. Save the resulting findings as a trace report in your workspace to document the root cause investigation before moving to requirements crystallization.
Requirements crystallization is needed for strategic initiatives lacking defined outcomes or cross-team problems requiring structured handoffs. It surfaces unstated assumptions, defines scope boundaries, and identifies missing acceptance criteria, saving these details as a spec for planners.
The best way to structure cross-team handoffs is through synthesis, merging the causal trace report and requirements spec into a unified deliverable. This ensures planners receive both the identified root causes and the crystallized scope boundaries for the ambiguous problem.
Yes, you can use this investigation method for strategic initiatives lacking defined outcomes. The requirements crystallization stage specifically surfaces unstated assumptions and defines scope boundaries, making it suitable for resolving ambiguous strategic problems.
OliverOuyangOrchestrate parallel hypothesis tracing and evidence collection for causal failure analysis.
HouseofmvpsGenerate step-by-step implementation plans with file paths and test commands.
cheafiRun a two-stage trace-and-requirements pipeline to resolve unclear root causes.
ccakmak60Enforce root-cause analysis before fixes across four debugging phases.
