Skill
ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway…
@evolution-foundationView SkillAutomation
Skill
/dev-deep-dive
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.
Install
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-deep-dive --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-deep-dive
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
dev-deep-dive.SKILL.mdname: dev-deep-dive
description: 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.
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)
Read more
name: dev-deep-dive description: 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.
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)
Other skills on evo-nexus.
@evolution-foundationView SkillSkill
create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the…
@evolution-foundationView SkillSkill
create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in…
@evolution-foundationView SkillSkill
create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a…
@evolution-foundationView SkillSkill
create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake…
@evolution-foundationView SkillSkill
create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description,…
@evolution-foundationView Skill