upgrade_plan

# upgrade_plan — Upgrade a Plan or Requirements Set > **CodeOps Skills Version**: 3.19.0 Plans and requirements are living documents. As CodeOps standards evolve, older artifacts drift out of date. This skill **detects** staleness, **assesses** gaps against current standards, **upgrades** documents while preserving all user-authored content, and **verifies** the result. This skill covers **upgrades only**. To create a new plan use the make_plan skill; to create a new requirements set use the make_requirements skill. > **Resolve paths layout-aware, and don't migrate layout here.** A plan/requirements set lives at a > flat path (`plans/<feature>/`, `requirements/`) or, in a nested-layout repo, under > `codeops/features/<f>/…` — resolve it via **[../../_shared/layout-convention.md](../../_shared/layout-convention.md)**. > This skill upgrades **content/version** in place; it never moves a repo between layouts. Converting > a flat repo to the nested `codeops/` layout is the **`setup_codeops`** skill's job — point the user > there for that, and keep upgrades within the existing layout. ## Which target? (branch first) Detect the target from the phrasing/arguments before doing anything else: | Trigger | Target | Directory | |---------|--------|-----------| | `upgrade_plan [feature-name]`, "upgrade my plan", "bring the plan up to date" | **Plan** | `plans/[feature-name]/` | | `upgrade_requirements`, "upgrade my requirements", "bring requirements up to date" | **Requirements** |...