refactor-planlisted

# Purpose Generate a structured refactoring plan for a proposed code change in the project's codebase. The plan includes current state analysis, impact analysis across repos, step-by-step migration, risk assessment, and a rollback strategy. The output is a markdown document that can be reviewed before execution begins. This skill plans only -- it does not execute code changes. Success criteria: every file cited in the plan was found via Grep/Glob (not guessed), the plan covers all affected repos in every language of the project's stack (see `.claude/project.json` → `stack`), and the rollback strategy is specific enough to execute without interpretation. Placeholders: `<mainApp>` = `project.json → mainApp`; `<device>` = `project.json → device` (the device/edge repo, if the project has one). # When to use - Renaming a type, table, or module across the codebase (e.g., renaming a legacy entity name to its new domain name). - Restructuring file layout or module boundaries within the main app or the device repo. - Extracting shared logic into a library or consolidating duplicated code. - Changing a WebSocket/SSE message format between a producer service (e.g., the device repo) and a consumer (e.g., the main app). - Migrating from one pattern to another (e.g., class-based to functional, eager init to lazy init). # When NOT to use - **Executing pure-function refactoring directly** -- use `functional-design` which applies changes via Edit. - **Deployment or environment rollback