planning-impact-analysis

Identify what the changes truly affect to avoid missing critical areas Short description of the change or goal Known modules/files/services Integrations and external contracts (API, events, queues) Identify entry points and the data/request path List affected components (UI/API/worker/DB/infra) List contracts: public APIs, events, formats, schemas Describe data impact: schema, migrations, indexes, integrity Mark likely regressions and higher-criticality hotspots

Affected areas

Interfaces / contracts

Data impact

Regression hotspots

</output_format> Impact areas are specific and verifiable External contracts are listed explicitly </quality_rules>