request-refactor-planlisted

# Request Refactor Plan Create a structured refactor plan through deep interview and codebase exploration, then file it as a Jira ticket for the team. ## What the User Provides $ARGUMENTS ## Workflow ### Step 1 — Understand the problem Ask the user for a detailed description of: - What problem they're trying to solve (not just "clean this up" — why does it matter?) - Any ideas they already have for the solution - What triggered this refactor now (new feature blocked by it? bug pattern? team pain?) ### Step 2 — Explore and verify Use the Explore agent to understand the current state: - What does the code actually look like today? - Does the problem the user described match what's in the codebase? - What's the test coverage of this area? - What other code depends on the area being refactored? - Any recent git history that explains why it got this way? Report back: "Here's what I found..." before proceeding. ### Step 3 — Consider alternatives Present 2-3 alternative approaches before interviewing on implementation. Ask: - "Have you considered [alternative]?" - "What makes your proposed approach better than [alternative]?" This surfaces assumptions and ensures the planned solution is the right one. ### Step 4 — Interview on implementation Go deep on the specifics. Be thorough — vague plans produce bad refactors: - **Scope**: What's changing? What's explicitly NOT changing? - **Interfaces**: Which public APIs / component props / service methods change shape? - **Dat