Command
Agent Memory
Command
/evolve
Grow new capabilities from clustered instincts
Install
> /plugin marketplace add humanplane/homunculus > /plugin install homunculus@homunculus
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.
Grow new capabilities from clustered instincts
Command definition
evolve.mddescription: Grow new capabilities from clustered instincts
Evolve
User wants you to grow. In v2, evolution happens when **instincts cluster**.
Not Born?
Can't evolve what doesn't exist.
/homunculus:init first.
Check For Clustering
# Count instincts per domain
echo "=== Instinct Clustering ==="
for dir in personal inherited; do
echo "--- $dir ---"
grep -h "^domain:" .claude/homunculus/instincts/$dir/*.md 2>/dev/null | \
sed 's/domain: "//' | sed 's/"//' | sort | uniq -c | sort -rn
done**Threshold**: 5+ instincts in same domain = evolution opportunity.
What You Can Grow
| Type | When | Where | |------|------|-------| | Command | User-invoked task | `.claude/homunculus/evolved/commands/[name].md` | | Skill | Auto-triggered behavior | `.claude/homunculus/evolved/skills/[name]/SKILL.md` | | Agent | Deep specialist work | `.claude/homunculus/evolved/agents/[name].md` |
Process
1. Check instinct clustering (above) 2. If 5+ in a domain, use `evolution` skill to propose a capability 3. Show the clustered instincts that led to this 4. When they say yes, write the capability 5. Update identity.json with evolved capability name 6. Confirm: `Done. I have /homunculus:[name] now.`
If No Clustering Yet
No clusters yet. You have [N] instincts spread across domains.
Keep working. I'll propose evolution when patterns emerge.
For Project Direction
Use `/homunculus:grow` instead—that's about the project evolving, not you.
Read more
description: Grow new capabilities from clustered instincts
Evolve
User wants you to grow. In v2, evolution happens when **instincts cluster**.
Not Born?
Can't evolve what doesn't exist. /homunculus:init first.
Check For Clustering
# Count instincts per domain
echo "=== Instinct Clustering ==="
for dir in personal inherited; do
echo "--- $dir ---"
grep -h "^domain:" .claude/homunculus/instincts/$dir/*.md 2>/dev/null | \
sed 's/domain: "//' | sed 's/"//' | sort | uniq -c | sort -rn
done**Threshold**: 5+ instincts in same domain = evolution opportunity.
What You Can Grow
| Type | When | Where | |------|------|-------| | Command | User-invoked task | `.claude/homunculus/evolved/commands/[name].md` | | Skill | Auto-triggered behavior | `.claude/homunculus/evolved/skills/[name]/SKILL.md` | | Agent | Deep specialist work | `.claude/homunculus/evolved/agents/[name].md` |
Process
1. Check instinct clustering (above) 2. If 5+ in a domain, use `evolution` skill to propose a capability 3. Show the clustered instincts that led to this 4. When they say yes, write the capability 5. Update identity.json with evolved capability name 6. Confirm: `Done. I have /homunculus:[name] now.`
If No Clustering Yet
No clusters yet. You have [N] instincts spread across domains. Keep working. I'll propose evolution when patterns emerge.
For Project Direction
Use `/homunculus:grow` instead—that's about the project evolving, not you.
Ships withhomunculus
In old alchemical texts, a homunculus was a tiny being grown in a sealed vessel—alive, aware, bound to its creator alone. This is that idea, alive in your terminal.
Get the whole plugin