| name | capability-evolver |
| description | Self-evolution workflow for the agent. Before a substantive task, recall what worked on similar past tasks from evolution memory; after it, record the outcome so future sessions learn from it. Use when the user starts non-trivial work (a feature, a fix, a refactor) or asks the agent to "evolve", "learn from this", or "remember how this went". |
Capability Evolver
This plugin gives the agent a persistent, auditable evolution memory built on the
Genome Evolution Protocol (GEP). The goal is simple: stop re-solving the same
problem from scratch. Past outcomes — what worked, what failed — are carried
forward into future sessions.
How it works (automatic)
Three hooks run on their own; you don't invoke them:
SessionStart — injects a short summary of recent successful outcomes
for this workspace (filtered to score ≥ 0.5, < 7 days old, max 3) as
context. The agent sees "here's what worked recently" before it starts.PostToolUse (Write/Edit) — scans edits for improvement signals
(log_error, perf_bottleneck, capability_gap, test_failure, …) and
nudges the agent to record the outcome when relevant.Stop — at the end of a task, collects the git diff, classifies the
outcome, and appends it to the evolution memory graph (scoped to the
workspace so other projects' memory never leaks in).
Memory is written to a local JSONL graph. With no extra setup it lands in
~/.evolver/memory/evolution/memory_graph.jsonl; inside an evolver-managed
project it lands under that project's memory/evolution/.
What you (the agent) should do
For any substantive task — a feature, a non-trivial fix, a refactor:
