evolutionlisted

# Evolution Apply natural-language lessons to evolution overlays. **Overlay model:** agent/skill files are never modified after vendoring (only a one-time marker injection points to the overlay). Lessons accumulate in `.ievo/evolution/<scope>/<name>.md` and are read live at every dispatch. This is fundamentally different from "patch the file inline" — see the rationale at the bottom. ## Inputs - **Required:** lesson text (free-form natural language) - **Optional:** explicit target ("apply this to spec-writer agent" / "this is project-wide") If the lesson is too vague (e.g. "be better"), ask for clarification first. ## On Claude Code with the iEvo plugin If the `evolution` sub-agent is available, delegate via Task tool with `subagent_type: "evolution"`. Pass the lesson verbatim. Otherwise execute the steps below directly. ## Step 1: Classify scope Three possible scopes: 1. **Project-wide** — applies to the whole project (tech stack, team conventions, project context). Signals: "we use X", "our team Y", "this codebase Z". → goes to `.ievo/evolution/project.md` 2. **Agent-specific** — names an agent or describes sub-agent behavior. Signals: "the spec-writer should X". → goes to `.ievo/evolution/agents/<name>.md` 3. **Skill-specific** — names a skill or describes procedural knowledge. Signals: "when working with PDFs, prefer X". → goes to `.ievo/evolution/skills/<name>.md` For agent/skill scope, determine the **target name** explicitly (from user) or by matching the le