evolve

Detect new components, fields, and patterns from completed epics and propose registry updates.

27|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/JeremyKalmus/parade --skill evolve-jeremykalmus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/JeremyKalmus/parade/tree/main/.claude/skills/evolve
Command: npx skills add https://github.com/JeremyKalmus/parade --skill evolve-jeremykalmus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture positive evolutions from epic execution by identifying newly added components, fields, patterns, and capabilities and updating design registries and agent knowledge accordingly.

Core Features & Use Cases

  • Detects and documents truly new additions across epics, updating design registries and knowledge bases
  • Automatically runs at epic completion or on demand via /evolve <epic-id>, with dry-run support
  • Generates evolution reports and suggests registry updates for components, fields, and patterns

Quick Start

Use the evolve skill to analyze a completed epic: /evolve <epic-id>

Frequently Asked Questions about evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically capture new design patterns and components from completed epics?

By comparing completed epic git history against existing design registries, you can identify truly new additions. This mechanism detects newly added components and patterns, proposing formal updates to keep your documentation accurate.

How do I update my design registry with new fields after finishing an epic?

Generate an evolution report by analyzing the completed epic's git history against your design registries. This report suggests specific updates for newly added components, fields, and patterns for you to review and apply.

Can I preview suggested registry updates before applying them to my knowledge base?

Yes, the system supports a dry-run mode that generates evolution reports without applying changes. You can review proposed registry updates and selectively apply only the additions you approve.

When should I run an epic evolution analysis on my git history?

Run epic evolution analysis at epic completion or on demand to capture newly added components and patterns. This ensures your design registries and agent knowledge bases stay synchronized with your actual codebase.

What is the best way to keep agent knowledge bases synchronized with new codebase patterns?

Automatically analyze completed epics to detect new patterns and propose optional agent prompt enhancements. This keeps agent knowledge bases synchronized with the latest codebase evolutions without manual documentation.

Does epic evolution analysis support selective application of identified pattern updates?

Yes, alongside dry-run support, the system offers selective apply options. You can review the proposed evolution report and selectively apply only the registry updates and agent knowledge enhancements you deem necessary.