gov-change-impact-analyzer

Analyze change impacts across requirements, design, stories, tests, and release scope.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-change-impact-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gov-change-impact-analyzer
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/gov-change-impact-analyzer
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-change-impact-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, trace-aware process to determine what changes downstream when a requirement, design decision, dependency, or bug is modified, reducing missed updates and release surprises.

Core Features & Use Cases

  • Trace-aware impact mapping: Walk links from requirements through architecture, stories, tests, and release artifacts to enumerate affected items.
  • Risk and confidence assessment: Classify impact severity (high/medium/low), call out blind spots, and state confidence levels for findings.
  • Follow-up generation and routing: Recommend or instantiate follow-up user stories (US/HUS), assign owners, and save a templated impact report for human review.
  • Use case: Run this skill after an API contract change to identify affected architecture sections, implementation stories, contract tests, and release notes, then create follow-up work and a migration plan.

Quick Start

Run the gov-change-impact-analyzer on the changed artifact and produce an impact report listing affected artifacts, risk level, confidence, and recommended follow-up tasks.

Frequently Asked Questions about gov-change-impact-analyzer

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

FAQPage Schema
How do I trace the downstream impact of a requirement or design change?▼

Change impact analysis assesses proposed or implemented changes during change requests or dependency updates to identify affected artifacts, required updates, and follow-up work across your project lifecycle.

What is the best way to assess risk and confidence for a dependency update?▼

Assess risk and confidence for a dependency update by classifying impact severity as high, medium, or low, while explicitly stating confidence levels and calling out blind spots in the findings.

How do I generate follow-up user stories after an API contract change?▼

Generate follow-up user stories after an API contract change by recommending or instantiating follow-up stories, assigning owners, and saving a templated impact report for human review and downstream routing.

Does impact analysis work for redesigns and bug fixes across release scope?▼

Impact analysis works for redesigns and bug fixes by analyzing proposed or implemented changes to identify affected artifacts within the release scope and producing trace-aware impact reports for follow-up story creation.

Can I automate release planning when modifying architecture decisions?▼

You can automate release planning when modifying architecture decisions by producing structured impact analyses that identify affected tests, recommend follow-up tasks, and instantiate execution-plan templates for downstream routing.