dev-deep-dive

@evolution-foundation · 收录于 5 天前 · 上游提交 2 个月前

Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.

场景问题排查需求澄清

适合你，如果问题原因和范围都不清晰，需要系统化分析。

/ 下载安装

https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-deep-dive ↗

/ 通过 npx 安装 校验哈希

npx oh-my-skill add evolution-foundation/evo-nexus/dev-deep-dive

/ 通过 bash 安装

curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- evolution-foundation/evo-nexus/dev-deep-dive

/ 已经装过?验证本机副本,不用重装

npx oh-my-skill verify evolution-foundation/evo-nexus/dev-deep-dive

安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。

509GitHub stars

~354上下文体积 · 单文件

索引托管

怎么用

商店整理自技能原文 · 版本 7f5dd76 · 表述以原文为准

它做什么

装上后，Claude 会先进行因果追踪（调用 @trail-tracer），再执行需求结晶（调用 @echo-analyst 和 dev-deep-interview），最后综合输出问题根因和修复规格，并交给 @compass-planner 规划修复。

什么时候触发

当问题的原因和范围都不明确时触发，例如生产问题原因和修复范围不清晰、bug 需要根因分析和修复标准、或战略问题不知构建什么。

装好后可以这样说

触发完整两阶段调查流程。

同样触发深层调查。

也会触发该技能。

技能原文 SKILL.md作者撰写 · Apache-2.0 · 7f5dd76

Dev Deep Dive

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

A two-stage investigation that combines causal tracing with requirements crystallization. Use when both the cause AND the scope of a problem are ambiguous.

Use When

Production issue with unclear cause AND unclear scope of fix
Bug report that needs both root cause analysis and clarification of "what does fixed look like?"
Strategic problem where you don't know what to build OR why the current state isn't working

Workflow

Stage 1 — Causal trace

Hand off to @trail-tracer:

Generate competing hypotheses
Collect evidence FOR and AGAINST each
Apply lenses (systems / premortem / science)
Identify the discriminating probe
Save report to workspace/development/debug/[C]trace-{topic}-{date}.md

Stage 2 — Requirements crystallization

Hand off to @echo-analyst + dev-deep-interview:

Surface unstated assumptions
Define scope boundaries
Identify missing acceptance criteria
Save spec to workspace/development/specs/[C]spec-{topic}-{date}.md

Stage 3 — Synthesis

Combine the trace report and the requirements spec
Output: a unified understanding of "what's broken AND what done looks like"
Hand off to @compass-planner to plan the actual fix

Pairs With

@trail-tracer (Stage 1)
@echo-analyst (Stage 2)
dev-deep-interview (Stage 2)
@compass-planner (Stage 3 handoff)

按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。

…