Identify strategic direction gaps between requirements and architecture.
npx skills add https://github.com/tody-agent/codymaster --skill cm-reactor
Please help me install this Agent Skill. Skill: cm-reactor Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-reactor Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-reactor
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.
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.
High-intent search queries and answers about installing and using this skill.
To refactor a large codebase with architecture misfit, apply a structured five-phase incremental migration process: assess gaps, map dependencies, design adapters, execute strangler fig migration, and verify transitions to realign direction without risky big-bang rewrites.
Safe legacy code migration uses the Strangler Fig pattern by creating adapters, implementing new functionality behind interfaces, and gradually migrating consumers while ensuring every step passes tests and changes are isolated with feature flags.
Mapping dependency blast radius requires analyzing touchpoints across the codebase before modifying architecture, utilizing code intelligence workflows to identify impacted consumers and safely plan incremental migrations.
Incremental migration is necessary when a large codebase faces feature drift, architecture misfit, or escalating tech debt, preventing futile rewrites by realigning strategic direction through adapter-first design and test-enabled transitions.
The TRIZ-based reactor approach specifically targets large codebases with escalating tech debt, applying a formal five-phase protocol to identify strategic direction gaps and enable safe, incremental migrations without losing system stability.
Executing phase-based migration involves following the ASSESS, MAP, DESIGN, EXECUTE, and VERIFY phases to guide safe transitions, mapping dependency touchpoints first, then using adapters and feature flags to incrementally migrate consumers.
velesarEvaluate project architecture alignment against ABB/SBB reference building blocks.
nksethDocument legacy system architecture and define an incremental migration strategy.
swannysecAnalyze Python and TypeScript codebases to map dependencies, blast radius, health, and execution flow.
pkuppensBackfill V-model traceability into brownfield codebases with retrofit artifacts.
