Trace root causes and crystallize requirements via a 2-stage interview process.
npx skills add https://github.com/Hyeonjun0527/yeon --skill deep-dive-hyeonjun0527
Please help me install this Agent Skill. Skill: deep-dive Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/deep-dive Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill deep-dive-hyeonjun0527
Deep Dive orchestrates a 2-stage pipeline that first investigates WHY something happened (trace) then precisely defines WHAT to do about it (deep-interview). The trace stage runs 3 parallel causal investigation lanes, and its findings feed into the interview stage via a 3-point injection mechanism — enriching the starting point, providing system context, and seeding initial questions. The result is a crystal-clear spec grounded in evidence, not assumptions.
Provide your problem statement to initiate the deep-dive flow and begin trace and interview.
High-intent search queries and answers about installing and using this skill.
Ambiguous bug investigations translate into actionable requirements through a 2-stage trace and interview process. This pipeline runs parallel causal investigation lanes to find root causes, then injects those trace findings into a deep-interview to crystallize evidence-based specs.
Requirements crystallization for early-stage product questions works best by orchestrating a structured trace phase before defining what to do. Multi-lane tracing investigates why a problem exists, and a 3-point injection mechanism feeds those findings into an interview stage for precise specifications.
Requirements planning workflows support resuming interrupted phases through persistent state execution. The process manages brownfield and greenfield detection, saves progress across trace and interview stages, and ensures seamless handoff to execution without losing intermediate causal findings.
A structured trace is needed before writing product requirements when facing ambiguous problems or bug investigations. It identifies root causes across parallel causal investigation lanes, ensuring the final crystallized requirements are grounded in evidence rather than initial assumptions.
Deep-dive handles handoff to execution plans by injecting trace findings into the interview initialization. It delivers an end-to-end workflow that seamlessly transitions from crystallized requirements directly into omc-plan and autopilot execution for immediate downstream action.
marcmunoz-unoRun a trace-to-interview pipeline to generate causal explanations and requirements specs.
INNERJOINTTrace root causes and produce interview-driven specifications for downstream planning.
jmstar85Trace root causes and interview to define actionable requirements.
kwt00Orchestrate a two-stage pipeline for causal investigation and requirements crystallization.
