Skip to content
Development
Command

/evolve

Analyze instincts and suggest or generate evolved structures

From plugin
ecc
239k109 skills72 agents109 commands7 hooks
+1
Install
> /plugin marketplace add affaan-m/ECC
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/evolve

Context preview

What this command does when you run it.

Analyze instincts and suggest or generate evolved structures

Command definition

evolve.md
name: evolve
description: Analyze instincts and suggest or generate evolved structures
command: true

Evolve Command

Implementation

Run the instinct CLI using the plugin root path:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]

Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):

python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]

Analyzes instincts and clusters related ones into higher-level structures:

  • **Commands**: When instincts describe user-invoked actions
  • **Skills**: When instincts describe auto-triggered behaviors
  • **Agents**: When instincts describe complex, multi-step processes

Usage

/evolve                    # Analyze all instincts and suggest evolutions
/evolve --generate         # Also generate files under evolved/{skills,commands,agents}

Evolution Rules

→ Command (User-Invoked)

When instincts describe actions a user would explicitly request:

  • Multiple instincts about "when user asks to..."
  • Instincts with triggers like "when creating a new X"
  • Instincts that follow a repeatable sequence

Example:

  • `new-table-step1`: "when adding a database table, create migration"
  • `new-table-step2`: "when adding a database table, update schema"
  • `new-table-step3`: "when adding a database table, regenerate types"

→ Creates: **new-table** command

→ Skill (Auto-Triggered)

When instincts describe behaviors that should happen automatically:

  • Pattern-matching triggers
  • Error handling responses
  • Code style enforcement

Example:

  • `prefer-functional`: "when writing functions, prefer functional style"
  • `use-immutable`: "when modifying state, use immutable patterns"
  • `avoid-classes`: "when designing modules, avoid class-based design"

→ Creates: `functional-patterns` skill

→ Agent (Needs Depth/Isolation)

When instincts describe complex, multi-step processes that benefit from isolation:

  • Debugging workflows
  • Refactoring sequences
  • Research tasks

Example:

  • `debug-step1`: "when debugging, first check logs"
  • `debug-step2`: "when debugging, isolate the failing component"
  • `debug-step3`: "when debugging, create minimal reproduction"
  • `debug-step4`: "when debugging, verify fix with test"

→ Creates: **debugger** agent

What to Do

1. Detect current project context 2. Read project + global instincts (project takes precedence on ID conflicts) 3. Group instincts by trigger/domain patterns 4. Identify:

  • Skill candidates (trigger clusters with 2+ instincts)
  • Command candidates (high-confidence workflow instincts)
  • Agent candidates (larger, high-confidence clusters)

5. Show promotion candidates (project -> global) when applicable 6. If `--generate` is passed, write files to:

  • Project scope: `~/.claude/homunculus/projects/<project-id>/evolved/`
  • Global fallback: `~/.claude/homunculus/evolved/`

Output Format

============================================================
  EVOLVE ANALYSIS - 12 instincts
  Project: my-app (a1b2c3d4e5f6)
  Project-scoped: 8 | Global: 4
============================================================

High confidence instincts (>=80%): 5

## SKILL CANDIDATES
1. Cluster: "adding tests"
   Instincts: 3
   Avg confidence: 82%
   Domains: testing
   Scopes: project

## COMMAND CANDIDATES (2)
  /adding-tests
    From: test-first-workflow [project]
    Confidence: 84%

## AGENT CANDIDATES (1)
  adding-tests-agent
    Covers 3 instincts
    Avg confidence: 82%

Flags

  • `--generate`: Generate evolved files in addition to analysis output

Generated File Format

Command

---
name: new-table
description: Create a new database table with migration, schema update, and type generation
command: /new-table
evolved_from:
  - new-table-migration
  - update-schema
  - regenerate-types
---

# New Table Command

[Generated content based on clustered instincts]

## Steps
1. ...
2. ...

Skill

---
name: functional-patterns
description: Enforce functional programming patterns
evolved_from:
  - prefer-functional
  - use-immutable
  - avoid-classes
---

# Functional Patterns Skill

[Generated content based on clustered instincts]

Agent

---
name: debugger
description: Systematic debugging agent
model: sonnet
evolved_from:
  - debug-check-logs
  - debug-isolate
  - debug-reproduce
---

# Debugger Agent

[Generated content based on clustered instincts]
Read more
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin