Dev Learner

Dev Learner

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

Meta-skill: scan the current conversation for patterns that appeared 3+ times and propose extracting them as reusable skills. The "self-improving workspace" feedback loop.

Use When

• A long session involved repeated workflows that aren't yet skills
• You want to formalize a pattern you keep manually invoking
• Post-EPIC retrospective: what should have been a skill but wasn't?

Do Not Use When

• Single-pattern conversation → no extraction value
• The pattern is too specific to one project → keep as agent memory
• The pattern is already a skill → just document it better

Workflow

Phase 1 — Pattern Detection

Scan the conversation for:

• Repeated workflows — same sequence of agents called 3+ times
• Repeated prompts — similar instructions issued repeatedly
• Repeated outputs — same artifact format produced multiple times
• Repeated handoffs — same agent pair invoked together repeatedly

Phase 2 — Extraction

For each detected pattern:

1. Name it (e.g., "PR review pipeline", "Debug investigation flow")
2. Describe the trigger
3. Document the steps
4. Identify the agents involved
5. Identify the inputs and outputs

Phase 3 — Proposal

Propose the new skill:

• Name: suggested skill name (dev-{action} if engineering, {prefix}-{action} otherwise)
• Trigger: when to invoke
• Workflow: the steps
• Pairs with: which agents/skills