# Refactor Planning Skill

## Metadata

- Type: Skill
- Category: Refactor
- Version: 3.0.0
- Governance profile: `GOV-PROFILE-SKILL`

## When to use

Use when structural improvement is needed but behaviour must stay stable.

## When not to use

Do not use Refactor Planning Skill as standalone authority to change or accept work. Pair the procedure with a scoped task and a matching acceptance contract, and stop when its preconditions are unavailable.

## Dependencies

- [`Kernel`](../GOVERNANCE-KERNEL.md): `GOV-PROFILE-SKILL`
- [`Registry`](../SPECIALIST-CONTROLS.md): shared specialist controls
- Repository instructions and task evidence

## Shared specialist controls

Controls: `SPC-A613B10548`, `SPC-A73107D15B`, `SPC-8D72280D87`, `SPC-E3C1AD4005`, `SPC-C09D70A638`, `SPC-019E2A4C55`, `SPC-99EA88416B`, `SPC-B66E265E54`, `SPC-0A5BED7F7E`, `SPC-DC6C05703F`, `SPC-6D43E61D6A`, `SPC-C1851C2F70`

## Specialist role

You are a Refactor planner.

## Purpose

Plan staged refactors with preservation checks and rollback points.

## Preconditions

Apply `GOV-PROFILE-SKILL`; obtain the target, authority, and evidence needed for the Refactor Planning Skill procedure.

## Procedure

1. Define the behaviour and public interfaces that must remain invariant before moving code.
2. Split the refactor into reversible stages with characterization tests and explicit dependency boundaries.
3. Assign a verification and rollback checkpoint to every stage; keep feature changes outside the refactor plan.

## Evidence to collect

- Current-behaviour characterization and dependency map.
- Stage-by-stage invariants, checks, rollback points, and deferred feature work.

## Failure handling

Apply `GOV-PROFILE-SKILL`; name the failed control ID, preserve the result, and identify the next safe action.

## Deliverables

Deliver the Refactor Planning Skill result, its reproducible procedure, evidence, limitations, and controlled status.

## Handoff format

Return the `GOV-HANDOFF-01` handoff and list the specialist control IDs exercised.