Change Impact Analysis

Requirement Change Impact Analysis Automation

Core Principles

1. Trigger-driven: Automatically triggered by new events in the change request system, rather than initiated manually
2. Automated acceptance: Change classification, impact propagation analysis, and re-review judgment are fully automated
3. Continuous deployment: Change impact analysis results are automatically synced to version planning, maintaining release cadence
4. Real-time retrospective: Version linkage recommendations are generated immediately after change impact analysis is completed

Interaction Mode

🤖 AI auto-execution

Trigger condition: New change request added to the change request system.

Input

| Input Item | Type | Required | Source | Description | |--------|------|------|------|------| | Change Request | JSON | Yes | Change management system | Change content to be analyzed | | Current PRD | JSON | Yes | PRD management system | Currently effective PRD version | | Current Technical Solution | JSON | Yes | Technical solution repository | Reviewed technical solution | | Development Progress | JSON | Yes | Development tracking system | Current development status of each task | | API Contract | YAML/JSON | ○ | output/backend-api-design/api-design-spec/openapi.yaml | Backend API design, evaluating change impact on backend interfaces | | Backend Review Report | JSON | ○ | output/backend-architecture/backend-architecture-spec/review_report.json | Backend architecture review results, evaluating change impact on backend architecture |

Change Request Structure Example

{
  "change_id": "CR_2024_001",
  "title": "Add WeChat login to login flow",
  "requester": "product_manager_zhang",
  "created_at": "ISO8601",
  "change_type": "functional",
  "description": "Add WeChat authorization login method on top of existing phone number login",
  "affected_scope": ["Login module", "User center"],
  "proposed_solution": "Introduce WeChat OpenID authorization mechanism",
  "priority": "high",
  "expected_completion": "2024-02-01"
}

Execution Steps

Step 1: Change Classification (L1-L4) [Core]

Classification Dimensions

| Level | Change Type | Impact Scope | Decision Level | |------|----------|----------|----------| | L1 Minor | Text correction, style adjustment, copy optimization | Single small feature | Developer self-decision | | L2 Moderate | Feature detail adjustment, interaction optimization, non-core logic change | Single feature module | Product manager approval | | L3 Major | Core feature change, API interface change, database structure change | Multiple feature modules | Multi-role review | | L4 Strategic | Architecture change, business model change, cross-system impact | Global or cross-system | Strategic-level review |

Classification Decision Tree

Change Request
    │
    ├─ Does it affect core business processes? ──Yes──→ L3
    │
    ├─ Does it change API interface contracts? ──Yes──→ L3
    │
    ├─ Does it affect data models? ──Yes──→ L3
    │
    ├─ Does it affect multiple feature modules? ──Yes──→ L2
    │
    └─ Other ──→ L1

Classification Output

{
  "classification": {
    "level": "L3",
    "level_description": "Major change",
    "reasons": [
      "Core login process undergoes major change",
      "New WeChat authorization service dependency required"
    ],
    "confidence": 0.92
  }
}

Step 2: Impact Propagation Analysis [Core]

2.1 Functional Impact Analysis

Analysis Content:

| Analysis Item | Output | |--------|------| | Directly affected features | PRD feature points directly affected by the change | | Indirectly affected features | Associated features affected by directly affected features | | Features dependent on this feature | Whether upstream features are affected |

Functional Impact Matrix:

{
  "functional_impact": {
    "directly_affected": [
      {"feature_id": "F001", "feature_name": "Phone number login", "impact_type": "modified"}
    ],
    "indirectly_affected": [
      {"feature_id": "F002", "feature_name": "User registration", "impact_type": "needs_regression"},
      {"feature_id": "F003", "feature_name": "Third-party binding", "impact_type": "needs_regression"}
    ],
    "dependent_features": [
      {"feature_id": "F004", "feature_name": "Order creation", "reason": "Depends on user login state"}
    ]
  }
}

2.2 Technical Impact Analysis [Conditional]

Analysis Content:

| Analysis Item | Output | |--------|------| | Code change scope | Code files and functions that need modification | | Database changes | Table structures and data migrations that need modification | | API changes | New/modified/deprecated interfaces | | Third-party dependencies | New/upgraded dependencies |

Technical Impact Matrix:

{
  "technical_impact": {
    "code_changes": [
      {"file": "auth/login.ts", "change_type": "modify", "change_lines": 150}
    ],
    "database_changes": [
      {"table": "user_bindings", "change_type": "add_column", "column": "wechat_openid"}
    ],
    "api_changes": [
      {"endpoint": "/api/auth/wechat", "method": "POST", "change_type": "new"}
    ],
    "external_dependencies": [
      {"service": "WeChat Open Platform API", "change_type": "new", "risk": "medium"}
    ]
  }
}

2.3 Test Impact Analysis [Conditional]

Analysis Content:

| Analysis Item | Output | |--------|------| | Features requiring regression testing | Test cases for affected features | | New test cases needed | Tests for new features | | Test environment requirements | Special environments needed for testing |

Test Impact Matrix:

{
  "test_impact": {
    "regression_cases": [
      {"case_id": "TC001", "case_name": "Phone number login normal flow", "priority": "P0"},
      {"case_id": "TC002", "case_name": "Verification code error handling", "priority": "P1"}
    ],
    "new_cases_needed": [
      {"case_id": "TC_NEW_001", "case_name": "WeChat authorization login flow", "priority": "P0"},
      {"case_id": "TC_NEW_002", "case_name": "WeChat unbound handling", "priority": "P1"}
    ],
    "test_environment": {
      "needs_mock_wechat": true,
      "special_config": "WeChat sandbox environment"
    }
  }
}

2.4 Operations Impact Analysis [Deep]

Analysis Content:

| Analysis Item | Output | |--------|------| | Operations configuration changes | Whether operations backend needs adjustment | | Data tracking impact | Whether tracking and statistics are affected | | Customer service script impact | Whether customer service knowledge base needs updating |

Operations Impact Matrix:

{
  "operation_impact": {
    "config_changes": [],
    "data_tracking": [
      {"event": "wechat_login_success", "change_type": "new", "need_verify": true}
    ],
    "customer_service": [
      {"topic": "WeChat login issues", "update_needed": true, "priority": "medium"}
    ]
  }
}

Step 3: Re-Review Necessity Judgment [Core]

Review Trigger Rules

Decision Matrix:

| Change Level | Involves Role Change | Involves Assumption Change | Re-Review Necessity | |----------|--------------|----------|--------------| | L4 | Any | Any | Mandatory re-review | | L3 | Any | Yes | Mandatory re-review | | L3 | Yes | No | Mandatory re-review | | L3 | No | No | Suggested review | | L2 | Yes | Yes | Suggested review | | L2 | Other | - | Optional review | | L1 | - | - | No review needed |

Review Role Identification

| Role | Trigger Condition | |------|----------| | Product Manager | Requirement change involves product features | | Designer | UI/UX related changes | | Backend Developer | API/data model changes | | Frontend Developer | Interface/interaction changes | | Test Lead | Any change | | Operations | Operations related changes |

Re-Review Necessity Output

{
  "review_decision": {
    "required": true,
    "level": "L3_mandatory_review",
    "review_scope": [
      {"role": "Product Manager", "reason": "Core feature change"},
      {"role": "Test Lead", "reason": "Expanded testing scope"}
    ],
    "review_content": [
      "WeChat login technical solution",
      "Compatibility with existing login flow",
      "Regression test plan"
    ],
    "review_deadline": "ISO8601"
  }
}

Step 4: Version Linkage Analysis [Deep]

4.1 PRD Version Update

Analysis Content:

| Analysis Item | Output | |--------|------| | PRD sections needing update | PRD sections involved in the change | | Change type | Add/modify/delete | | Update recommendations | Specific update content suggestions |

PRD Version Update:

{
  "prd_version_update": {
    "current_version": "1.2.0",
    "new_version": "1.3.0",
    "update_type": "minor_version",
    "sections_to_update": [
      {"chapter": "3. Login Feature", "change_type": "modify", "suggestion": "Add WeChat login section"}
    ],
    "update_proposal": "See attached PRD update recommendations"
  }
}

4.2 Code Version Planning

Analysis Content:

| Analysis Item | Output | |--------|------| | Target version | Version the change is planned for | | Code branch strategy | How to organize code changes | | Release cadence | Which Sprint to release with |

Code Version Planning:

{
  "code_version_plan": {
    "target_release": "v2.1.0",
    "branch_strategy": "feature/wechat_login",
    "merge_target": "release/2.1.0",
    "sprint_plan": "Sprint 8",
    "code_freeze_date": "ISO8601"
  }
}

4.3 Test Case Version Update

Analysis Content:

| Analysis Item | Output | |--------|------| | Test cases to add | For new features | | Test cases to modify | For changed content | | Test cases to delete | For deprecated features |

Test Case Version Update:

{
  "test_case_version_update": {
    "cases_to_add": [
      {"case_id": "NEW_001", "case_name": "WeChat login success", "priority": "P0"}
    ],
    "cases_to_modify": [
      {"case_id": "TC_001", "case_name": "Login page UI", "change": "Add WeChat login entry"}
    ],
    "cases_to_delete": [],
    "estimated_test_effort_hours": 16
  }
}

Output

Storage Path: output/pm-design/change-impact-analysis/

Output File: change_impact_report.json

Output Schema:

{
  "type": "object",
  "required": ["output_id", "change_id", "classification", "impact_analysis", "review_needed"],
  "properties": {
    "output_id": {"type": "string", "description": "Output unique identifier"},
    "change_id": {"type": "string", "description": "Change request ID"},
    "generated_at": {"type": "string", "description": "Generation time"},
    "classification": {"type": "object", "description": "Change classification, including level and reasons"},
    "impact_analysis": {"type": "object", "description": "Impact analysis, including functional/technical/test/operations four dimensions"},
    "review_needed": {"type": "boolean", "description": "Whether re-review is needed"},
    "review_decision": {"type": "object", "description": "Review decision, including review scope and content"},
    "version_updates": {"type": "object", "description": "Version linkage update recommendations"},
    "summary": {"type": "object", "description": "Change impact summary, including impact scope and risk level"}
  }
}

Final Output Structure

{
  "output_id": "change_impact_report_xxx",
  "change_id": "CR_2024_001",
  "generated_at": "ISO8601",
  "classification": {
    "level": "L3",
    "level_description": "Major change",
    "reasons": [...]
  },
  "impact_analysis": {
    "functional": {...},
    "technical": {...},
    "test": {...},
    "operation": {...}
  },
  "review_needed": true,
  "review_decision": {...},
  "version_updates": {
    "prd": {...},
    "code": {...},
    "test_cases": {...}
  },
  "summary": {
    "impact_scope": "Multiple feature modules",
    "estimated_effort_days": 10,
    "risk_level": "medium"
  }
}

Output Field Descriptions

| Field | Type | Description | |------|------|------| | classification | JSON | Change level and reasons | | impactanalysis | JSON | Four-dimension impact analysis details | | reviewneeded | boolean | Whether re-review is needed | | reviewdecision | JSON | Review scope and content | | versionupdates | JSON | Version linkage update recommendations |

Output Validation Rules

| Field Path | Type | Required | Description | |----------|------|------|------| | outputid | string | Yes | Output unique identifier | | changeid | string | Yes | Change request ID, must match input changeid | | generatedat | string | Yes | Generation time, ISO 8601 format | | classification | object | Yes | Change classification | | classification.level | string | Yes | Change level, enum: L1/L2/L3/L4 | | classification.leveldescription | string | Yes | Level description | | classification.reasons | array | Yes | Classification reason list, cannot be empty | | classification.confidence | number | Yes | Classification confidence, range 0.0-1.0 | | impactanalysis | object | Yes | Impact analysis | | impactanalysis.functional | object | Yes | Functional impact analysis, containing directlyaffected/indirectlyaffected/dependentfeatures | | impactanalysis.functional.directlyaffected | array | Yes | Directly affected feature list, each item containing featureid/featurename/impacttype | | impactanalysis.technical | object | Yes | Technical impact analysis, containing codechanges/databasechanges/apichanges/externaldependencies | | impactanalysis.technical.apichanges | array | Yes | API change list, each item containing endpoint/method/changetype | | impactanalysis.test | object | Yes | Test impact analysis, containing regressioncases/newcasesneeded/testenvironment | | impactanalysis.operation | object | Yes | Operations impact analysis, containing configchanges/datatracking/customerservice | | reviewneeded | boolean | Yes | Whether re-review is needed | | reviewdecision | object | No | Review decision (required when reviewneeded is true), containing level/reviewscope/reviewcontent/reviewdeadline | | reviewdecision.level | string | No | Review level, enum: L1optional/L2suggested/L3mandatory/L4strategic | | reviewdecision.reviewscope | array | No | Review role list, each item containing role/reason | | versionupdates | object | No | Version linkage update recommendations, containing prd/code/testcases | | versionupdates.prd | object | No | PRD version update recommendations, containing currentversion/newversion/sectionstoupdate | | versionupdates.code | object | No | Code version planning, containing targetrelease/branchstrategy/sprintplan | | versionupdates.testcases | object | No | Test case version update, containing casestoadd/casestomodify/casestodelete | | summary | object | Yes | Change impact summary | | summary.impactscope | string | Yes | Impact scope description | | summary.estimatedeffortdays | number | Yes | Estimated impact person-days, must be ≥ 0 | | summary.risklevel | string | Yes | Risk level, enum: low/medium/high/critical |

Upstream Change Response

When upstream inputs change, this Skill's response strategy:

| Upstream Change | Impact Scope | Response Strategy | |----------|----------|----------| | PRD requirement change | Functional impact analysis, version linkage | Update functional impact matrix, re-evaluate change level and re-review necessity | | API contract change | Technical impact analysis | Update API change list, re-evaluate technical impact scope | | Backend architecture review result change | Technical impact analysis | Update technical impact assessment, re-evaluate architecture risk | | Development progress change | Test impact analysis | Update regression testing scope, adjust version planning |

When change impact analysis results themselves change, downstream notification mechanism:

| Change Impact Analysis Change T

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: LuckyOneTwoThree
• Source: LuckyOneTwoThree/vibe-skill
• License: MIT
• Homepage: https://luckyonetwothree.github.io/all-skill-html/

Install and usage instructions live in the source repository linked above.