skills.rest
SSiertsema
SSiertsemaCOMMUNITY
Explore all skills by this author →
GitHub

impact-analysis

Analyze proposed changes across a traceability graph to identify affected artifacts and risks.

1|Updated Nov 29, 2025
Search Tags:#traceability#risk-assessment#blast-radius#change-management#impact-analysis#stakeholder-communication#graph-analysis
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill impact-analysis-ssiertsema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impact-analysis
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/impact-analysis/skills/impact-analysis
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill impact-analysis-ssiertsema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams understand the ripple effects of proposed changes by analyzing a change against a traceability graph to identify affected artifacts and potential risks.

Core Features & Use Cases

  • Identifies affected artifacts (requirements, stories, tests, deployed services, dependent teams, external consumers)
  • Computes blast radius and estimates effort and risk
  • Suggests phasing and produces a stakeholder-communication plan
  • Consumes traceability-matrix output to drive the analysis

Quick Start

Provide a proposed change with source artifact IDs and let the tool derive upstream and downstream implications

Frequently Asked Questions about impact-analysis

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

FAQPage Schema
How do I analyze the impact of a proposed change across a traceability graph?▼

Impact analysis across a traceability graph identifies affected artifacts, computes blast radius, and estimates effort and risk. By providing source artifact IDs and upstream/downstream relationships, the tool derives implications and suggests phasing along with a stakeholder-communication plan.

What is needed to calculate blast radius and risk for requirements changes?▼

Calculating blast radius and risk requires a traceability-matrix output and an explicit change description with type and source artifact IDs. Clear upstream and downstream relationships are also necessary to identify affected tests, deployed services, and dependent teams.

How do I identify affected artifacts and dependent teams before implementing a change?▼

Identify affected artifacts by analyzing a proposed change against a traceability-matrix output. The analysis maps upstream and downstream dependencies to highlight affected requirements, stories, tests, deployed services, dependent teams, and external consumers.

Can I generate a stakeholder-communication plan from a traceability matrix?▼

Yes, a stakeholder-communication plan is generated by consuming a traceability-matrix output alongside explicit change descriptions. The analysis suggests phasing and produces targeted communications for affected dependent teams and external consumers.

Does impact analysis work without explicit upstream and downstream relationships?▼

No, clear upstream and downstream relationships are required to map changes across the traceability graph. Without explicit source artifact IDs and a traceability-matrix output, the tool cannot accurately compute blast radius or identify affected artifacts.

Related Skills

Explore More Software Engineering Skills→
ReadyStateChangeReadyStateChange

maintaining-artifact-consistency

Synchronize downstream and upstream artifacts when truth changes across the artifact chain.

Official
Advanced
jasonwilmotjasonwilmot

safe-refactor

Plan code refactors with blast-radius analysis and rollback strategies.

Community
Advanced
fabioabrfabioabr

gitnexus-impact-analysis

Analyze dependencies and execution flows to identify impact and blast radius of code changes.

Community
Advanced
bs-koobs-koo

impact-analysis

Trace ID chains to identify impacted artifacts and estimate change effort.

Community
Advanced