plan-evolve

# /plan-evolve This is exactly what I wanted — can we evolve this to its next version? Treat what shipped as version 1, now plan version 2 — what would that be? ## Frame Something shipped. It worked. Now the user wants the next version of it. The **target** can be anything that has a current state: - A plan (`PLAN.md` or a plan file) - A repo, codebase, or system - A document, spec, or skill - A feature, product, or process Version numbers are immaterial — "v1 → v2" is just shorthand for "what shipped → what's next." ## Find v1 Identify what counts as v1: - A `PLAN.md` or plan file in the current directory or `.claude/plans/` - A plan or target the user points you to - **The current state of the target itself** — if no plan artifact exists, what is built / written / deployed today *is* v1 If no plan was provided, do not block and do not demand one — the current state of the target is the floor you evolve from. Only ask the user if the target itself is ambiguous. ## The work V1 is the floor, not the ceiling. The next version means: - What did v1 leave on the table? - What would you do differently now that v1 exists? - What new possibilities does v1 unlock that weren't visible before? - Where did v1 make pragmatic compromises that the next version can resolve? Don't re-plan from scratch. Evolve. V1's decisions are load-bearing until proven otherwise. Output a next-version plan. If v1 was a plan, match its format — same structure, upgraded content. If v1 was a target...