Evolve Skill

Purpose

Capture positive evolutions from completed epics - the new components, fields, patterns, and capabilities that were added during implementation. This complements /retro (which captures failures) by documenting what was successfully created.

Key Principle: Only propose updates for truly new additions. If an epic used existing patterns and components, no updates are needed.

When to Use

• Automatically invoked at /run-tasks Step 10 (epic completion)
• User invokes /evolve <epic-id> directly
• After any epic that added new UI components, data fields, or patterns

Entry Points