analyze-impact

Analyze proposed changes to surface affected components and required updates.

1|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/asermax/claude-plugins --skill analyze-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-impact
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/analyze-impact
Command: npx skills add https://github.com/asermax/claude-plugins --skill analyze-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing proposed changes to understand their effects on existing features, dependencies, and documentation to support proactive decision-making and planning.

Core Features & Use Cases

  • Capture change impact across feature specs, architecture decisions, and design patterns.
  • Surface affected components and required updates across docs, ADRs, and design artifacts.
  • Use Case: When planning a modification, run impact analysis to identify ripple effects and necessary follow-up work.

Quick Start

Describe the change you are considering to trigger the impact analysis workflow.

Frequently Asked Questions about analyze-impact

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

FAQPage Schema
How do I analyze the impact of code changes on existing features and dependencies?

Impact analysis evaluates proposed changes against feature specs, ADRs, and design patterns. It surfaces affected components and required updates, producing an actionable report detailing impact, risk levels, and recommended next steps.

What is the best way to identify ripple effects when modifying architecture decisions?

Architecture change impact analysis applies a workflow across design patterns and ADRs to identify ripple effects. It generates a report detailing affected documents and necessary follow-up work for proactive planning.

How do I generate an actionable report for risk levels and affected documents?

Impact analysis produces an actionable report detailing risk levels and affected documents. By evaluating proposed changes against existing dependencies and design patterns, it outlines recommended next steps for planning.

Can I use impact analysis to surface required updates across feature specs and ADRs?

Yes, impact analysis surfaces required updates across feature specs and ADRs. It evaluates proposed changes against existing documentation and design patterns to identify affected components and necessary modifications.

What do I need to provide to trigger an impact analysis workflow for my proposed changes?

You need to describe the change you are considering. The impact analysis workflow then evaluates this description against existing feature specs, dependencies, and design artifacts to quantify the change impact.

When should I not use an automated impact analysis workflow for software planning?

Impact analysis is designed for planned modifications where feature specs, ADRs, and design patterns exist. It may not be suitable for exploratory changes lacking formal documentation or when analyzing undocumented dependencies.