plan-evolve

Generates a next-version plan by evolving an existing plan, codebase, or shipped artifact.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill plan-evolve-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-evolve
Source: https://github.com/allemaar/open-skills/tree/main/skills/plan-evolve
Command: npx skills add https://github.com/allemaar/open-skills --skill plan-evolve-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After something ships, teams often struggle to decide what the next iteration should contain without discarding what already works. This Skill treats the shipped state as v1 and produces a structured v2 plan that builds on it rather than starting over. ## Core Features & Use Cases - v1 Detection: Locates an existing plan artifact (PLAN.md or files in .claude/plans/) or treats the current state of the target as v1 when no plan exists. - Evolutionary Planning: Identifies what v1 left on the table, which compromises to resolve, and what new possibilities v1 unlocks, while preserving load-bearing decisions. - Format Matching: Mirrors the structure of the original plan when one exists, marking what is new, changed, or carried forward. - Use Case: After shipping a feature, ask what v2 would look like and receive a phased next-version plan that respects prior decisions and highlights deliberate changes. ## Quick Start Ask the agent to evolve this project to its next version and produce a v2 plan based on the current state.

Frequently Asked Questions about plan-evolve

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

FAQPage Schema
How do I plan the next version of a shipped feature?

Point the skill at the feature or its existing plan and ask what v2 would look like. It treats the shipped state as v1, identifies gaps and compromises, and outputs a phased next-version plan that preserves prior decisions.

What happens if there is no existing plan file to evolve?

The skill does not block when no PLAN.md or plan artifact exists. It treats the current state of the target—code, document, or system—as v1 and produces a new phased plan from that baseline.

Can plan-evolve handle targets other than plan documents?

Yes, the target can be a repository, codebase, system, document, spec, skill, feature, product, or process. Anything with a current state qualifies as v1 and can be evolved into a next-version plan.

Does evolving a plan discard the original v1 decisions?

No, v1 decisions are treated as load-bearing until proven otherwise. The skill marks what is new, changed, or carried forward, and every change requires an explicit reason rather than versioning up for its own sake.

What should I do after generating a v2 plan?

The skill suggests follow-up steps: inspect the plan phase-by-phase with plan-deep-dive, get focused review with insight-critique, and execute it with plan-execute once approved.