Name: evolve
Author: zzh0u

Prompt file imported from zzh0u/gojet (.claude/commands/evolve.md). Fill in {{CLAUDE_PLUGIN_ROOT}} before use. Copyright stays with the author.

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 --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

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

Install evolve and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Evolve Command ## Implementation Run the instinct CLI using the plugin root path: ```bash python3 "{{CLAUDE_PLUGIN_ROOT}}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate] ``` Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation): ```bash 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 --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 `~/.claude/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 `~/.claude/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: - ~/.claude/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: - ~/.claude/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: - ~/.claude/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 ```markdown --- 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 ```markdown --- 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 ```markdown --- 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] ```

{ "prompt": "# Evolve Command\n\n## Implementation\n\nRun the instinct CLI using the plugin root path:\n\n```bash\npython3 \"{{CLAUDE_PLUGIN_ROOT}}/skills/continuous-learning-v2/scripts/instinct-cli.py\" evolve [--generate]\n```\n\nOr if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):\n\n```bash\npython3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]\n```\n\nAnalyzes instincts and clusters related ones into higher-level structures:\n- **Commands**: When instincts describe user-invoked actions\n- **Skills**: When instincts describe auto-triggered behaviors\n- **Agents**: When instincts describe complex, multi-step processes\n\n## Usage\n\n```\n/evolve # Analyze all instincts and suggest evolutions\n/evolve --domain testing # Only evolve instincts in testing domain\n/evolve --dry-run # Show what would be created without creating\n/evolve --threshold 5 # Require 5+ related instincts to cluster\n```\n\n## Evolution Rules\n\n### → Command (User-Invoked)\nWhen instincts describe actions a user would explicitly request:\n- Multiple instincts about \"when user asks to...\"\n- Instincts with triggers like \"when creating a new X\"\n- Instincts that follow a repeatable sequence\n\nExample:\n- `new-table-step1`: \"when adding a database table, create migration\"\n- `new-table-step2`: \"when adding a database table, update schema\"\n- `new-table-step3`: \"when adding a database table, regenerate types\"\n\n→ Creates: `/new-table` command\n\n### → Skill (Auto-Triggered)\nWhen instincts describe behaviors that should happen automatically:\n- Pattern-matching triggers\n- Error handling responses\n- Code style enforcement\n\nExample:\n- `prefer-functional`: \"when writing functions, prefer functional style\"\n- `use-immutable`: \"when modifying state, use immutable patterns\"\n- `avoid-classes`: \"when designing modules, avoid class-based design\"\n\n→ Creates: `functional-patterns` skill\n\n### → Agent (Needs Depth/Isolation)\nWhen instincts describe complex, multi-step processes that benefit from isolation:\n- Debugging workflows\n- Refactoring sequences\n- Research tasks\n\nExample:\n- `debug-step1`: \"when debugging, first check logs\"\n- `debug-step2`: \"when debugging, isolate the failing component\"\n- `debug-step3`: \"when debugging, create minimal reproduction\"\n- `debug-step4`: \"when debugging, verify fix with test\"\n\n→ Creates: `debugger` agent\n\n## What to Do\n\n1. Read all instincts from `~/.claude/homunculus/instincts/`\n2. Group instincts by:\n - Domain similarity\n - Trigger pattern overlap\n - Action sequence relationship\n3. For each cluster of 3+ related instincts:\n - Determine evolution type (command/skill/agent)\n - Generate the appropriate file\n - Save to `~/.claude/homunculus/evolved/{commands,skills,agents}/`\n4. Link evolved structure back to source instincts\n\n## Output Format\n\n```\n🧬 Evolve Analysis\n==================\n\nFound 3 clusters ready for evolution:\n\n## Cluster 1: Database Migration Workflow\nInstincts: new-table-migration, update-schema, regenerate-types\nType: Command\nConfidence: 85% (based on 12 observations)\n\nWould create: /new-table command\nFiles:\n - ~/.claude/homunculus/evolved/commands/new-table.md\n\n## Cluster 2: Functional Code Style\nInstincts: prefer-functional, use-immutable, avoid-classes, pure-functions\nType: Skill\nConfidence: 78% (based on 8 observations)\n\nWould create: functional-patterns skill\nFiles:\n - ~/.claude/homunculus/evolved/skills/functional-patterns.md\n\n## Cluster 3: Debugging Process\nInstincts: debug-check-logs, debug-isolate, debug-reproduce, debug-verify\nType: Agent\nConfidence: 72% (based on 6 observations)\n\nWould create: debugger agent\nFiles:\n - ~/.claude/homunculus/evolved/agents/debugger.md\n\n---\nRun `/evolve --execute` to create these files.\n```\n\n## Flags\n\n- `--execute`: Actually create the evolved structures (default is preview)\n- `--dry-run`: Preview without creating\n- `--domain <name>`: Only evolve instincts in specified domain\n- `--threshold <n>`: Minimum instincts required to form cluster (default: 3)\n- `--type <command|skill|agent>`: Only create specified type\n\n## Generated File Format\n\n### Command\n```markdown\n---\nname: new-table\ndescription: Create a new database table with migration, schema update, and type generation\ncommand: /new-table\nevolved_from:\n - new-table-migration\n - update-schema\n - regenerate-types\n---\n\n# New Table Command\n\n[Generated content based on clustered instincts]\n\n## Steps\n1. ...\n2. ...\n```\n\n### Skill\n```markdown\n---\nname: functional-patterns\ndescription: Enforce functional programming patterns\nevolved_from:\n - prefer-functional\n - use-immutable\n - avoid-classes\n---\n\n# Functional Patterns Skill\n\n[Generated content based on clustered instincts]\n```\n\n### Agent\n```markdown\n---\nname: debugger\ndescription: Systematic debugging agent\nmodel: sonnet\nevolved_from:\n - debug-check-logs\n - debug-isolate\n - debug-reproduce\n---\n\n# Debugger Agent\n\n[Generated content based on clustered instincts]\n```", "variables": [ "CLAUDE_PLUGIN_ROOT" ], "notes": "Cluster related instincts into skills, commands, or agents", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/zzh0u/gojet", "path": ".claude/commands/evolve.md", "ref": "726b2d24421b6e208c3498193bbebfed98786675", "url": "https://github.com/zzh0u/gojet/blob/726b2d24421b6e208c3498193bbebfed98786675/.claude/commands/evolve.md", "key": "zzh0u/gojet/.claude/commands/evolve.md" } } }

evolve

About

Evolve Command

Implementation

Usage

Evolution Rules

→ Command (User-Invoked)

→ Skill (Auto-Triggered)

→ Agent (Needs Depth/Isolation)

What to Do

Output Format

Flags

Generated File Format

Command

Skill

Agent

Install evolve and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews