evolve

Analyze completed plan diffs and route learnings to agent templates and docs.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/danalexilewis/taskgraph --skill evolve-danalexilewis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/danalexilewis/taskgraph/tree/main/.cursor/skills/evolve
Command: npx skills add https://github.com/danalexilewis/taskgraph --skill evolve-danalexilewis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-plan pattern mining to review completed plan execution for anti-patterns and route learnings to agent templates and docs. It enables a targeted post-mortem that informs templates like implementer.md and quality-reviewer.md and updates to docs/skills.

Core Features & Use Cases

  • Diff-based analysis of plan changes to surface anti-patterns.
  • Routing learnings to agent templates (e.g., implementer.md, quality-reviewer.md) and to docs/skills.
  • Supports multi-agent orchestration prior to the plan-merge step, and returns structured findings for action.

Quick Start

Invoke evolve after a plan completes to extract diffs and route learnings to templates and docs.

Frequently Asked Questions about evolve

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

FAQPage Schema
How do I identify anti-patterns from plan diffs after a project completes?

Analyzing plan diffs for anti-patterns involves inspecting completed plan execution changes to surface implementation issues. It extracts structural diffs from the most recent plan and generates structured findings to inform cross-team learning and post-mortem reviews.

What is plan-diff analysis and when do I need it for software engineering workflows?

Plan-diff analysis is a post-plan pattern mining technique that reviews completed plan changes for implementation anti-patterns. You need it after a plan completes to route extracted learnings to agent templates and docs, enabling targeted post-mortems for cross-team development.

How do I route learnings from plan reviews to agent templates and docs?

Routing learnings to agent templates and docs is achieved by analyzing plan diffs and generating structured findings. The process targets templates like implementer.md and quality-reviewer.md, updating durable knowledge across docs/skills for future use.

Can I use plan-evolve workflows for multi-agent orchestration prior to plan-merge?

Plan-evolve workflows support multi-agent orchestration prior to the plan-merge step. By invoking diff analysis after a plan completes, the process returns structured findings that route learnings to agent templates and docs for action.

What are the limitations of analyzing plan diffs for anti-patterns?

Analyzing plan diffs for anti-patterns targets only the most recent plan execution and requires a completed plan to extract changes. It focuses strictly on post-plan pattern mining and routing learnings to templates, not pre-execution validation.