refactor-planlisted

# Purpose Generate a structured refactoring plan for a proposed code change: current state, cross-repo impact, step-by-step migration order, risks, and rollback. The output is a markdown document reviewed before execution — this skill plans only, never edits code. Success: every cited file was found via Grep/Glob, all affected repos in every stack language are covered, and the rollback is executable without interpretation. # Rules (never violate) 1. Read-only: Read/Grep/Glob only — no file is ever modified. 2. Every file cited in the plan is a real Grep/Glob result, never a guess. 3. Blast radius over 50 files → stop and escalate to the user before continuing. 4. Save the plan to the workspace task dir (`.../plan/README.md`), never inside a code repo. 5. Rollback must be specific — commit references, migration file names, revert order. 6. Schema changes go through migrations (landing before dependent code), never manual DDL. # Resources - Read `resources/planning-procedure.md` when building the plan: the 7-step procedure with checkpoints, self-check, mistakes, escalation triggers, and what to surface. - Read `resources/plan-template.md` when writing the output: the template, save-location contract, length budget, a full worked rename example, and failure modes. # How to use ## What it does Writes a refactoring plan for a change you are considering — and nothing else. It greps the codebase for every real reference, maps which repos and files are hit, orders steps so no