change-impact
Performs evidence-backed impact analysis before high-risk code, data, or interface changes and reconciles the planned impact with the actual diff afterward.
What it does
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, 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.
Quality judgment
Comprehensive, well-structured skill with clear pre/post-change phases, routing rules, evidence requirements, and sensible anti-patterns. Examples are brief and illustrative rather than worked-through, and some artifact references (MAP, STATUS, LOG) assume a specific ecosystem without definition, slightly limiting portability.