cm-reactor

What problem does it solve?

When the code works but the direction is wrong, you don't debug — you REACT. TRIZ-powered protocol for pivoting large codebases without losing stability. Large software projects frequently face shifting requirements, misaligned architectures, and accumulating tech debt that makes big rewrites risky. This skill provides a formal, incremental approach to re-align direction without destabilizing the system.

Core Features & Use Cases

• Phase-based migration without big-bang rewrites: ASSESS, MAP, DESIGN, EXECUTE, VERIFY to guide safe transitions.
• Dependency analysis: map touchpoints and blast radius before changing anything (with optional code intelligence workflows).
• Strangler Fig migration: create adapters, implement new functionality behind interfaces, and gradually migrate consumers.
• Safe, test-driven progress: every step must pass tests; commits are clearly labeled with reactor milestones; feature flags and adapters help isolate changes.
• Tooling integration: coordinates with CodyMaster core skills such as cm-brainstorm-idea, cm-codeintell, cm-planning, cm-execution, cm-tdd, cm-clean-code, cm-debugging, and cm-continuity to manage the migration lifecycle.

Quick Start

Start by running a reactor assessment to identify misalignment between requirements, architecture, and tech debt, then follow the five-phase Migration Path to implement an incremental Strangler Fig migration.