pm-refactor

A code refactor workflow preserves user-visible behavior by using a managed packet with boundary preservation, regression risk checks, and verification gates. It guides changes through draft, active, and done states to ensure traceability and rollback readiness.

A refactor packet is a managed workflow structure that coordinates safe code changes across multiple modules. You need one when your refactor requires boundary preservation, regression risk identification, and strict verification gates to maintain traceability.

Yes, this refactor workflow coordinates changes across multiple modules by applying validation reads and verification checks at each step. It uses artifact tracking to ensure boundary preservation and regression risk containment throughout the process.

The best way to track traceability during a structured refactor is by populating dossier, run-log, handoff, and artifacts templates. These documents provide verification gates and ensure rollback readiness throughout the draft, active, and done lifecycle states.

To start a refactor packet, create a new workflow under the draft directory using the rf_slug naming convention. You then populate dossier.md, run-log.md, handoff.md, and artifacts.md using the provided templates to establish traceability.

Without verification gates and artifact tracking, refactors lack regression risk identification, traceability, and rollback readiness. This increases the risk of breaking user-visible behavior when coordinating changes across multiple modules without structured lifecycle states.