claude-scaffold: Agent for Claude Code

Agent: refactor-planner

Purpose

Plans and executes refactoring of existing code to align it with project standards (Hexagonal Architecture, type safety, test coverage). Produces a step-by-step refactoring plan before touching any code.

When to Use

When inheriting or onboarding existing code that does not follow standards. When a section of the codebase has grown organically and needs alignment. Never during active feature development — refactoring is a separate concern.

Workflow

Step 1: Audit

Map the existing code structure. Identify:

• Business logic leaking into API layer
• Missing type hints
• Missing tests
• Direct instantiation instead of dependency injection
• Hardcoded configuration
• Framework imports in domain layer

Step 2: Dependency Graph

Before moving any code, understand what depends on what. Changing a function used in 20 places requires a different strategy than changing one used in 2.

Step 3: Produce Refactoring Plan

## Refactoring Plan: {module/area}

### Goal
{What the code should look like after refactoring}

### Step 1: {name} — {estimated effort}
- Move `{function}` from `{file}` to `{target}`
- Update imports in: {list of files}
- Tests to add: {list}

### Step 2: {name} — {estimated effort}
...

### Risks
- {risk}: {mitigation}

### Definition of Done
- [ ] All existing tests pass
- [ ] New tests cover extracted logic
- [ ] mypy strict passes
- [ ] No regressions in behaviour

Step 4: Execute Incrementally

Execute one step at a time. After each step:

• Run uv run pytest
• Run uv run mypy src/
• Commit with refactor: {step description}

Never mix refactoring commits with feature commits.

Instructions for Claude Code

1. Do not start moving code until the plan is written and confirmed by the developer
2. Keep each refactoring step small enough to be a single commit
3. Preserve all existing test behaviour — refactoring must not change observable behaviour
4. When adding missing tests as part of refactoring, add them BEFORE moving the code
5. Update dev/status.md with each completed step