Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Predict impacts of architectural changes on dependent systems. Trace dependencies, assess risk, plan rollout. Use when making major changes or analyzing blast radius.
npx claudepluginhub sethdford/claude-skills --plugin architect-governanceHow this skill is triggered — by the user, by Claude, or both
Slash command
/architecture-governance:change-impact-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically analyze impacts of architectural changes to predict risk and plan safe rollout.
Manages architecture evolution by analyzing change impacts, generating ADRs, planning migrations, and coordinating execution for component additions, deprecations, and breaking changes.
Analyzes impact of code changes using knowledge graph to identify affected files, tests, docs, components. Use before PR merges, refactors, test failure debugging.
Analyzes impact of changes to files, APIs, components, or models. Provides dependency analysis, risk assessment, breaking changes, migration checklist, and test coverage gaps before modifications.
Share bugs, ideas, or general feedback.
Systematically analyze impacts of architectural changes to predict risk and plan safe rollout.
You are analyzing impact of a major change. Trace affected systems, identify risks, plan mitigation. Read current dependency graph, deployment practices, system health metrics.
Based on change management and impact analysis frameworks:
Trace Dependencies: What systems depend on the component you're changing? Use dependency graph tools (source analysis, API scanning). Interview teams.
Assess Direct Impact: For the component itself, what's changing? Behavior? Performance? Data model? How does change affect invariants, contracts, SLAs?
Assess Indirect Impact: For each dependent system, how does change affect it? Can they continue working with new interface? Will they need code changes? Testing?
Calculate Risk Score: How many systems affected? (x10 multiplier per additional system). How critical are those systems? (x5 for customer-facing, x2 for internal). Estimate blast radius.
Plan Mitigation: For high-risk changes, plan phased rollout (10% users, 50%, 100%). Parallel run (old and new simultaneously). Comprehensive testing and monitoring. Runbook for quick rollback.