change-impact
affaan-m/ECC
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, and compare planned impact with actual diff after implementation. Covers call paths, data/schema, API contracts, tests, docs, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.