Refactor Plan

This is a Hermes-native refactor-plan workflow skill.

Why This Exists

refactor-plan exists because boundary-changing refactors bounced between goal planning and behavior-preserving cleanup with neither owning the execution shape: the phase order, the per-phase rollback, and the files table that make a large refactor reviewable and abortable.

Do Not Use When

• The refactor's direction is still contested or the goal itself needs consensus planning; use ulw-plan.
• The work is deletion-first cleanup with no boundary changes; use omh-ai-slop-cleaner.
• The plan is done and the claim is that work is complete; use omh-verification-gate for the evidence close.
• The version bump carries a security advisory, a CVE, or a leaked secret; use omh-security-event-response, which owns containment and closure.

Examples

Good example: