/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