change-impact-analyzer

Analyze the blast radius of a proposed product change across technical surfaces.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill change-impact-analyzer-machenjie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-impact-analyzer
Source: https://github.com/machenjie/rd-skills/tree/main/src/professional-skills/change-impact-analyzer
Command: npx skills add https://github.com/machenjie/rd-skills --skill change-impact-analyzer-machenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly surprises by exposing the full blast radius of a proposed change across product behavior, data, APIs, integrations, security, testing, deployment, and documentation before implementation or release.

Core Features & Use Cases

  • Surface-by-surface impact analysis: Classify impact as Direct, Indirect, Downstream, Latent, None (with rationale), or Unknown (with proposed owner).
  • Compatibility and rollback safety: Assess backward compatibility, migration readiness, and whether rollback is safe without data intervention.
  • Specialist routing and release readiness: Identify which gates and specialist skills must be engaged based on discovered risks, and capture open questions as actionable placeholders.

Quick Start

Ask change-impact-analyzer to inventory and classify every surface impacted by your proposed change, including compatibility, rollback implications, specialist routing, and the remaining open questions.

Frequently Asked Questions about change-impact-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the blast radius of an API contract change before release?

Change impact analysis classifies the blast radius of API contract changes across behavior, data schemas, integrations, and frontend surfaces to quantify release readiness and rollback safety prior to deployment.

What is change impact analysis and when do I need it for data migrations?

Change impact analysis inventories downstream consumers and compatibility risks for data migrations, classifying surfaces as Direct, Indirect, or Latent to ensure rollback safety without data intervention.

How do I identify specialist routing requirements for cross-ownership change requests?

Analyze cross-ownership change requests to surface downstream consumer risks, classify impact across API contracts and observability, and route open questions to proposed specialist owners for release gate approval.

Can I assess backward compatibility and rollback safety for a proposed product change?

Yes, compatibility and rollback analysis evaluates backward compatibility, migration readiness, and rollback safety without data intervention, producing structured impact classifications for pre-implementation planning.

What's the best way to inventory impacted surfaces for release readiness planning?

Inventory impacted surfaces by classifying behavioral, domain model, API, security, testing, and deployment risks, capturing open questions with proposed owners to ensure complete release readiness.

When should I not use change impact analysis for a proposed product change?

Change impact analysis is unnecessary for isolated changes with no downstream consumers, API contract modifications, data schema updates, or cross-ownership dependencies where rollback safety is already guaranteed.