1.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| change-impact-analysis | Use before implementation when a proposed code, configuration, data, or workflow change has uncertain callers, compatibility effects, dependencies, or blast radius. Return an impact analysis without implementing it. |
Change Impact Analysis
Use before a change when its consumers, compatibility effects, or blast radius are uncertain.
Workflow
- Define the proposed change and the behavior or contract it affects.
- Locate direct callers, related implementations, shared helpers, configuration, generated output, and relevant tests. Start with exact-path and symbol searches; broaden only when the flow is unclear.
- Trace likely impact through runtime paths, persisted data, client integrations, deployment, and documentation as applicable.
- Identify compatibility concerns, failure modes, security or data-loss risks, and dependencies on version or environment. Before confirming external compatibility or recommending an approach, MUST apply the planning checkpoint in
technical-researchand attach matching evidence or mark the assumption unresolved. - Separate confirmed impacts from assumptions and unknowns. Do not treat a possible downstream effect as a fact without evidence.
- Recommend proportionate verification tied to the risks found.
Return a concise impact map: affected areas, evidence, risks, unknowns, and checks. Do not implement the proposal unless asked.