| name | refactor |
| description | Route refactor using exact migration registry [{"unit":"refactor/default","routing":{"negative_boundaries":["Fix the incorrect billing result and add a regression test.","Implement a new billing workflow from the approved specification.","Simplify this one small function by removing incidental nesting."],"positive_triggers":["Refactor the billing module structure while preserving all external behavior.","Restructure these related files around one responsibility with baseline and regression checks.","Transform this implementation to remove coupling without adding features."]}}]. |
Refactor with Behavioral Proof
Improve one named structural concern while preserving externally observable behavior.
Protocol
- Validate the repository-relative target and inspect its callers, dependencies, tests, and guidance.
- State the structural problem, affected boundary, behavior invariants, excluded cleanup, and rollback point.
- Establish a focused baseline with the repository's existing checks. If the baseline fails, separate that evidence from any proposed refactor.
- Transform the smallest coherent slice. Keep compatibility surfaces stable and avoid new product behavior.
- Repeat the baseline after each slice, then complete proportionate broader checks for affected integrations.
- Inspect the final diff for hidden behavior change, dependency expansion, test weakening, or unrelated churn.
- Complete the repository-required review and verification gates before claiming completion.
Result
Report the structural concern, preserved invariants, changed boundaries, baseline/post-change evidence, and any unverified behavior.
Pack handoff
This canonical skill is distributed from the core plugin. Its legacy development-pack payload remains immutable migration provenance and is not a runtime routing surface.
{
"positive_triggers": [
"Refactor the billing module structure while preserving all external behavior.",
"Restructure these related files around one responsibility with baseline and regression checks.",
"Transform this implementation to remove coupling without adding features."
],
"negative_boundaries": [
"Fix the incorrect billing result and add a regression test.",
"Implement a new billing workflow from the approved specification.",
"Simplify this one small function by removing incidental nesting."
]
}