Semantic-Safe Module Boundary Migration

This skill is a Pipeline + Reviewer for module, package, and ownership-boundary migrations driven by caller-visible semantic surface. Choose it only when boundary is the primary thing changing and callers should keep seeing materially the same discovery path, exports, behavior, errors, and side effects.

Use When

Use when the user asks to:

• move a module to a new package, directory, layer, or ownership boundary without breaking callers
• split a large module into smaller internal modules while keeping the same public entry points
• consolidate duplicate modules under one canonical boundary and migrate callers safely
• migrate consumers from a legacy import path, adapter, or facade to a new boundary in stages
• preserve discovery, exports, signatures, errors, and side effects while ownership or location changes

Do not use for: