What problem does it solve? Before committing to a feature design, teams need to understand the existing code they will touch, extend, or replace. This Skill maps the relevant internal components, their coupling, and blast radius, then assigns each part a change disposition (reuse, extend, refactor, or replace) with migration impact and risk rationale. ## Core Features & Use Cases - Component and Coupling Mapping: Traces requirements to concrete modules, services, and interfaces, rendering dependencies as a Mermaid flowchart with change-disposition classes. - Change Disposition Decisions: Justifies reuse-as-is, extend, refactor, or replace for each component, with migration paths, backward compatibility, and de-risking strategies for refactors and replacements. - Use Case: When requirements call for real-time Kubernetes state instead of polling reconciliation, the analysis locates the reconciliation loop and its consumers, recommends replacing the polling loop with an event-driven consumer behind a feature flag, and keeps the output contract stable. ## Quick Start Run the create-codebase-analysis skill against the approved requirements document for the current feature to produce a codebase-analysis.md artifact.
