SKILL44architecture-engineering
Planning Safe Refactors
Turns broad structural changes into releasable migration slices with protected contracts, explicit seams, verification evidence, and rollback paths.
Primary benefit
Reduces refactor blast radius while keeping the system releasable and making structural progress observable at every slice.When to use
Use when a structural refactor crosses multiple modules, dependencies, data flows, or deployments and cannot be completed safely as one atomic change without a large blast radius.
When not to use
Do not use when the change is small, local, behavior-preserving, and safely reviewable and reversible as one atomic change.
Use cases
Replace a shared framework or dependency without migrating every consumer in one release
Gradually extract a legacy capability while keeping old and new paths verifiable during migration
Example prompts
Use planning-safe-refactors to map the blast radius of this structural change and produce incremental slices with seams, regression evidence, rollback, and cleanup conditions.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill planning-safe-refactorsPowerShell
./install.ps1 --skill planning-safe-refactorsChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.