# Request Refactor Plan

> DEPRECATED. Prefer `/improve-codebase-architecture` for refactor discovery, then `/to-issues` for tickets. Do not use unless user explicitly says `/request-refactor-plan`.

- Skill: `redpanda-data/request-refactor-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add redpanda-data/request-refactor-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/redpanda-data/request-refactor-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: redpanda-data (https://skillmd.com/u/redpanda-data)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/redpanda-data/request-refactor-plan

---


> Deprecated: prefer replacement named in description. Keep only for backward compatibility.

# Request Refactor Plan

## Process

### 1. Understand
Ask problem + solution ideas. What wrong? What "better" mean?

### 2. Verify
Agent(subagent_type=Explore) verify claims vs codebase. Check real state.

### 3. Alternatives
Ask other approaches + trade-offs.

### 4. Drill Into Details
Scope, interface contracts (before/after), data migrations, backcompat, incremental path.

### 5. Test Coverage
Assess coverage. Insufficient -> ask test plan first.

### 6. Tiny Commits
Each step: deployable alone, tests green, one change.

### 7. GitHub Issue

`gh issue create`:

    ## Problem Statement
    What wrong and why.

    ## Solution
    Chosen approach and rationale.

    ## Commits
    1. [description] -- what changes, tests green
    2. [description] -- what changes, tests green

    ## Decisions
    Key decisions + rationale from interview.

    ## Testing
    New tests needed, existing tests changed.

    ## Out of Scope
    What NOT touched.