impact-analysis

Analyzes cascading impact of architectural changes across technical, organisational, financial, and risk dimensions.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill impact-analysis-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact-analysis
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/impact-analysis
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill impact-analysis-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating the blast radius of an architectural change—such as a database migration, cloud move, or API deprecation—requires coordinated analysis across technical, organisational, financial, and risk dimensions, which is slow and error-prone when done ad hoc. ## Core Features & Use Cases - Parallel Multi-Dimension Analysis: Launches four agents simultaneously to assess technical dependencies, team and training impacts, cost projections, and risk scoring. - Structured Impact Report: Synthesizes findings into an executive summary, impact score (0-10), financial year-by-year breakdown, risk matrix, implementation checklist, and rollback procedure. - Configurable Scope and Depth: Supports system, programme, or enterprise scope with quick, standard, or deep analysis levels. - Use Case: Before migrating OrderService from Oracle to PostgreSQL, run the skill to get a full impact report covering integration changes, training needs, 3-year cost projections, and a scored risk register for the architecture governance board. ## Quick Start Ask the AI to run an impact analysis on your proposed architectural change, providing the current state, proposed state, and affected systems.

Frequently Asked Questions about impact-analysis

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

FAQPage Schema
How do I assess the impact of an architectural change before committing to it?

Invoke the skill with a change description, then provide the current state, proposed state, affected systems, and timeline. It runs four parallel analyses and returns a scored impact report with a recommendation to proceed, defer, or stop.

What dimensions does an architecture impact analysis cover?

It covers four dimensions: technical (dependencies, integrations, data migration), organisational (teams, training, process changes), financial (implementation and operational costs over three years), and risk (probability-impact scoring with mitigations).

Can I adjust the scope and depth of the impact analysis?

Yes. Use the --scope flag to set the blast radius to system, programme, or enterprise, and --depth to choose quick, standard, or deep analysis. Defaults are system scope and standard depth.

How are risks scored in the impact report?

Each risk is scored as Probability (1-5) multiplied by Impact (1-5), giving a score from 1 to 25. Risks scoring 12 or above receive proposed mitigations in the risk register.

When should I not use a parallel multi-agent impact analysis?

For small, well-understood changes with a single affected system and no cross-team dependencies, a lightweight manual review is faster. The full analysis is best suited to migrations, platform changes, and enterprise-wide deprecations.