Semantic-Safe Implementation Refactor

This skill is a Pipeline + Reviewer for semantic-preserving implementation replacement. Choose it only when implementation is the primary thing changing and the external surface, module boundary, and technology model are intended to stay materially stable.

Use When

Use when the user asks to:

• replace brittle legacy logic with a cleaner implementation behind the same interface or contract
• rewrite a component, service, handler, or workflow without intentionally changing its public behavior
• extract a cleaner subsystem behind an existing route, schema, event, adapter, or facade
• introduce a new implementation path and cut traffic over after equivalence is proven
• reimplement from observed semantics instead of copying the old control flow

Do not use for: