evolve

name	evolve
description	Imported from everything-codex command evolve
version	0.1.0
source	fork
checksum	64c48085380696d7a7685037c21b358fd0162fd87a8611bfd2373146211eff81
updated_at	"2026-02-11T01:29:16.000Z"
layer	quality

---

name: evolve description: Cluster related instincts into skills, commands, or agents command: true

Evolve Command

Native Subagent Protocol (Codex)

Codex supports native subagents. Delegate with spawn_agent, coordinate with send_input, collect via wait_agent, and clean up with close_agent.

Execution preference:

1. Use native subagents first for independent workstreams (parallel when possible).
2. Merge results in main thread and run final verification.
3. Fallback only when delegation is blocked: use the [ANALYST]/[ARCHITECT]/[EXECUTOR]/[REVIEWER] structure in a single response.

Minimal orchestration pattern:

spawn_agent -> send_input (optional) -> wait_agent -> close_agent

Implementation

Run the instinct CLI using the Codex home path:

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

Or if CODEX_HOME is not set (manual installation):

python3 ~/.codex/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 --domain testing   # Only evolve instincts in testing domain
$evolve --dry-run          # Show what would be created without creating
$evolve --threshold 5      # Require 5+ related instincts to cluster

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. Read all instincts from ~/.codex/homunculus/instincts/
2. Group instincts by:
   • Domain similarity
   • Trigger pattern overlap
   • Action sequence relationship
3. For each cluster of 3+ related instincts:
   • Determine evolution type (command/skill/agent)
   • Generate the appropriate file
   • Save to ~/.codex/homunculus/evolved/{commands,skills,agents}/
4. Link evolved structure back to source instincts

Output Format

🧬 Evolve Analysis
==================

Found 3 clusters ready for evolution:

## Cluster 1: Database Migration Workflow
Instincts: new-table-migration, update-schema, regenerate-types
Type: Command
Confidence: 85% (based on 12 observations)

Would create: $new-table command
Files:
  - ~/.codex/homunculus/evolved/commands/new-table.md

## Cluster 2: Functional Code Style
Instincts: prefer-functional, use-immutable, avoid-classes, pure-functions
Type: Skill
Confidence: 78% (based on 8 observations)

Would create: functional-patterns skill
Files:
  - ~/.codex/homunculus/evolved/skills/functional-patterns.md

## Cluster 3: Debugging Process
Instincts: debug-check-logs, debug-isolate, debug-reproduce, debug-verify
Type: Agent
Confidence: 72% (based on 6 observations)

Would create: debugger agent
Files:
  - ~/.codex/homunculus/evolved/agents/debugger.md

---
Run `$evolve --execute` to create these files.

Flags

• --execute: Actually create the evolved structures (default is preview)
• --dry-run: Preview without creating
• --domain <name>: Only evolve instincts in specified domain
• --threshold <n>: Minimum instincts required to form cluster (default: 3)
• --type <command|skill|agent>: Only create specified type

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]