Analyze epic histories to detect new patterns and propose registry updates.
npx skills add https://github.com/dot-do/dotdo --skill evolve-dot-do
Please help me install this Agent Skill. Skill: evolve Source: https://github.com/dot-do/dotdo/tree/main/.claude/skills/evolve Command: npx skills add https://github.com/dot-do/dotdo --skill evolve-dot-do
Automatically identifies and records positive evolutions introduced during epic implementation, ensuring design registries stay aligned with actual enhancements.
Run /evolve <epic-id> to analyze a completed epic and generate a formal evolution report.
High-intent search queries and answers about installing and using this skill.
To update a design system registry after an epic, analyze epic histories to identify new patterns and components, then compare changes against existing registries to propose updates for genuine innovations.
The best way to detect new components introduced during epic implementation is to analyze epic histories against design registries, which identifies newly added fields and patterns while avoiding duplicates.
An evolution report supports design system governance by detailing proposed registry changes and actionable recommendations, ensuring design registries stay aligned with actual enhancements from completed epics.
Yes, you can preview proposed design registry updates without applying them by using an optional dry-run, which generates an evolution report detailing the detected changes and proposed actions safely.
To prevent duplicate pattern entries when managing design registries, validate detected changes by comparing them against existing registries, ensuring only truly new additions are proposed for updates.
You should analyze epic histories for pattern management when applied to completed epics or on-demand, allowing you to capture positive evolutions and formally record new patterns introduced during implementation.
diegosanchespereira1Facilitate structured post-epic retrospectives with story analysis and action items.
zby...
nomograph-aiSync local AI skills, agents, and rules with remote registries via CLI.
JeremyKalmusDetect new components, fields, and patterns from completed epics and propose registry updates.
