Run causal trace lanes and evidence-grounded interviews to generate requirements specs.
npx skills add https://github.com/solitude6060/Yao-skills --skill deep-dive-solitude6060
Please help me install this Agent Skill. Skill: deep-dive Source: https://github.com/solitude6060/Yao-skills/tree/main/skills/deep-dive Command: npx skills add https://github.com/solitude6060/Yao-skills --skill deep-dive-solitude6060
Deep-dive turns ambiguous problems into evidence-backed requirements by running a structured root-cause trace and then conducting a requirements interview grounded in that trace.
Use deep-dive for an ambiguous bug or improvement request by running it with your problem statement so it investigates cause and produces a requirements spec.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for ambiguous incidents requires a structured trace-then-interview pipeline. This Skill resolves unclear causes by running evidence-driven causal trace lanes first, then conducting a targeted interview to define actions precisely and generate a requirements specification.
Investigating bugs in a brownfield codebase involves replacing manual exploration with trace-derived system context. The Skill proposes three parallel causal hypotheses—implementation, config orchestration, and measurement mismatch—then confirms one lane before tracing the actual issue.
Yes, causal investigation can triage workflow routing failures by applying a three-lane hypothesis ranking mechanism. It isolates the confirmed failure lane from implementation, orchestration, and artifact mismatch perspectives before generating a final specification.
Trace-to-interview injection enriches feature exploration by seeding the interview initialization with trace findings, replacing brownfield exploration with system context, and formulating the first interview questions from per-lane unknowns to ground the requirements.
Yes, deep-dive generates a requirements specification after causal tracing. It produces a deep-interview standard spec that includes a dedicated Trace Findings section and then bridges directly to execution orchestration for the confirmed actions.
You should avoid a two-phase trace-then-interview approach when the incident cause is already explicitly known or when the problem lacks sufficient system artifacts for evidence-grounded tracing. It is designed specifically for ambiguous problems requiring deep investigation.
neurofooPerform iterative root cause analysis by repeatedly asking why.
Remaker-DigitalCoordinate versioned bridge thread proposals, reviews, and verifications via INDEX.md.
Pryma-TechOrchestrate competing tracer hypotheses to explain observed Claude team-mode results.
kwt00Orchestrate a two-stage pipeline for causal investigation and requirements crystallization.
