ba-impact-analysis

Generate an Impact Analysis package across six BA domains.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill ba-impact-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-impact-analysis
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/ba-impact-analysis
Command: npx skills add https://github.com/Yukine5377/common --skill ba-impact-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps business analysts assess the impact of a change request by analyzing feasibility and scope across six BA domains, and generating ready-to-use outputs for review and implementation.

Core Features & Use Cases

  • Identify and categorize impact across six BA groups: function, process, data, UI, integration, and stakeholders.
  • Produce a structured Impact Analysis document, risk/dependency notes, and a BA work list.
  • Generate stakeholder questions and outputs ready for CR/BRD preparation.

Quick Start

Provide the change request details (objective, context, related UC/US) and I will generate the Impact Analysis package.

Frequently Asked Questions about ba-impact-analysis

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

FAQPage Schema
How do I perform an impact analysis for a change request?

To perform an impact analysis, you provide the change request details including objective, context, and related use cases. The system then assesses feasibility and scope across six BA domains to generate a ready-to-use analysis package.

What is business analysis impact assessment across six domains?

Business analysis impact assessment identifies change request effects across six domains: function, process, data, UI, integration, and stakeholders. This structured evaluation guides feasibility, scope, and risk documentation for review and implementation.

How do I prepare a BRD or SRS update from a change request?

You prepare BRD or SRS updates by analyzing the change request impact. The process generates structured outputs including stakeholder questions, risk notes, and a BA work list to directly support CR and BRD preparation.

Can I generate stakeholder questions and risk notes for a change request automatically?

Yes, you can generate stakeholder questions and risk notes automatically. By processing the change request context and objectives, the system produces structured dependency notes and stakeholder queries for review.

What do I need to start documenting change request impacts for business analysis?

To start documenting change request impacts, you need the change request details such as its objective, context, and related use cases or user stories. This input allows the generation of the complete impact analysis package.

Does impact analysis cover integration and data changes for requirements?

Yes, impact analysis covers integration and data changes. It systematically categorizes effects across function, process, data, UI, integration, and stakeholders to ensure comprehensive scope and risk assessment.