需求变更影响分析自动化

核心原则

1. 触发器驱动：由变更请求系统新增事件自动触发，而非人工发起
2. 自动化验收：变更分类、影响传播分析、重评审判断全流程自动化
3. 持续部署：变更影响分析结果自动同步到版本规划，保持发布节奏
4. 实时复盘：变更影响分析完成后即时生成版本联动建议

交互模式

🤖 AI自动执行

触发条件：变更请求系统新增变更请求。

输入

变更请求结构示例

{
  "change_id": "CR_2024_001",
  "title": "登录流程增加微信登录",
  "requester": "product_manager_zhang",
  "created_at": "ISO8601",
  "change_type": "functional",
  "description": "在现有手机号登录基础上增加微信授权登录方式",
  "affected_scope": ["登录模块", "用户中心"],
  "proposed_solution": "引入微信OpenID授权机制",
  "priority": "high",
  "expected_completion": "2024-02-01"
}

执行步骤

Step 1: 变更分类（L1-L4）

#### 分类维度

#### 分类决策树

变更请求
    │
    ├─ 是否影响核心业务流程？ ──是──→ L3
    │
    ├─ 是否改变API接口契约？ ──是──→ L3
    │
    ├─ 是否影响数据模型？ ──是──→ L3
    │
    ├─ 是否影响多个功能模块？ ──是──→ L2
    │
    └─ 其他 ──→ L1

#### 分类输出

{
  "classification": {
    "level": "L3",
    "level_description": "重大变更",
    "reasons": [
      "核心登录流程发生重大变化",
      "需要新增微信授权服务依赖"
    ],
    "confidence": 0.92
  }
}

Step 2: 影响传播分析

#### 2.1 功能影响分析

分析内容：

功能影响矩阵：

{
  "functional_impact": {
    "directly_affected": [
      {"feature_id": "F001", "feature_name": "手机号登录", "impact_type": "modified"}
    ],
    "indirectly_affected": [
      {"feature_id": "F002", "feature_name": "用户注册", "impact_type": "needs_regression"},
      {"feature_id": "F003", "feature_name": "第三方绑定", "impact_type": "needs_regression"}
    ],
    "dependent_features": [
      {"feature_id": "F004", "feature_name": "订单创建", "reason": "依赖用户登录态"}
    ]
  }
}

#### 2.2 技术影响分析

分析内容：

技术影响矩阵：

{
  "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": "微信开放平台API", "change_type": "new", "risk": "medium"}
    ]
  }
}

#### 2.3 测试影响分析

分析内容：

测试影响矩阵：

{
  "test_impact": {
    "regression_cases": [
      {"case_id": "TC001", "case_name": "手机号登录正常流程", "priority": "P0"},
      {"case_id": "TC002", "case_name": "验证码错误处理", "priority": "P1"}
    ],
    "new_cases_needed": [
      {"case_id": "TC_NEW_001", "case_name": "微信授权登录流程", "priority": "P0"},
      {"case_id": "TC_NEW_002", "case_name": "微信未绑定处理", "priority": "P1"}
    ],
    "test_environment": {
      "needs_mock_wechat": true,
      "special_config": "微信沙箱环境"
    }
  }
}

#### 2.4 运营影响分析

分析内容：

运营影响矩阵：

{
  "operation_impact": {
    "config_changes": [],
    "data_tracking": [
      {"event": "wechat_login_success", "change_type": "new", "need_verify": true}
    ],
    "customer_service": [
      {"topic": "微信登录问题", "update_needed": true, "priority": "medium"}
    ]
  }
}

Step 3: 重评审必要性判断

#### 评审触发规则

决策矩阵：

#### 评审角色识别

#### 重评审必要性输出

{
  "review_decision": {
    "required": true,
    "level": "L3_mandatory_review",
    "review_scope": [
      {"role": "产品经理", "reason": "核心功能变更"},
      {"role": "测试负责人", "reason": "测试范围扩大"}
    ],
    "review_content": [
      "微信登录技术方案",
      "与现有登录流程的兼容性",
      "回归测试计划"
    ],
    "review_deadline": "ISO8601"
  }
}

Step 4: 版本联动分析

#### 4.1 PRD版本更新

分析内容：

PRD版本更新：

{
  "prd_version_update": {
    "current_version": "1.2.0",
    "new_version": "1.3.0",
    "update_type": "minor_version",
    "sections_to_update": [
      {"chapter": "3.登录功能", "change_type": "modify", "suggestion": "增加微信登录章节"}
    ],
    "update_proposal": "详见附件PRD更新建议"
  }
}

#### 4.2 代码版本规划

分析内容：

代码版本规划：

{
  "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": {
    "cases_to_add": [
      {"case_id": "NEW_001", "case_name": "微信登录成功", "priority": "P0"}
    ],
    "cases_to_modify": [
      {"case_id": "TC_001", "case_name": "登录页面UI", "change": "增加微信登录入口"}
    ],
    "cases_to_delete": [],
    "estimated_test_effort_hours": 16
  }
}

输出

存储路径：output/pm-design/change-impact-analysis/

输出文件：change_impact_report.json

输出Schema：

{
  "type": "object",
  "required": ["output_id", "change_id", "classification", "impact_analysis", "review_needed"],
  "properties": {
    "output_id": {"type": "string", "description": "输出唯一标识"},
    "change_id": {"type": "string", "description": "变更请求ID"},
    "generated_at": {"type": "string", "description": "生成时间"},
    "classification": {"type": "object", "description": "变更分类，包含级别和原因"},
    "impact_analysis": {"type": "object", "description": "影响分析，包含功能/技术/测试/运营四维度"},
    "review_needed": {"type": "boolean", "description": "是否需要重评审"},
    "review_decision": {"type": "object", "description": "评审决策，包含评审范围和内容"},
    "version_updates": {"type": "object", "description": "版本联动更新建议"},
    "summary": {"type": "object", "description": "变更影响摘要，包含影响范围和风险等级"}
  }
}

最终输出结构

{
  "output_id": "change_impact_report_xxx",
  "change_id": "CR_2024_001",
  "generated_at": "ISO8601",
  "classification": {
    "level": "L3",
    "level_description": "重大变更",
    "reasons": [...]
  },
  "impact_analysis": {
    "functional": {...},
    "technical": {...},
    "test": {...},
    "operation": {...}
  },
  "review_needed": true,
  "review_decision": {...},
  "version_updates": {
    "prd": {...},
    "code": {...},
    "test_cases": {...}
  },
  "summary": {
    "impact_scope": "多个功能模块",
    "estimated_effort_days": 10,
    "risk_level": "medium"
  }
}

输出字段说明

输出校验规则

上游变更响应

当上游输入发生变更时，本Skill的响应策略：

当变更影响分析结果自身变更时，对下游的通知机制：

决策规则

强制重评审规则

特殊处理规则

质量检查

Quality Check

影响范围穷举检查清单

• [ ] 功能影响：直接/间接/依赖功能已识别
• [ ] 技术影响：代码/数据库/API/依赖已识别
• [ ] 测试影响：回归/新增测试用例已识别
• [ ] 运营影响：配置/数据/客服已识别

降级策略

上游文件缺失降级方案

数据获取说明

当上游文件缺失时，需用户提供以下信息以支撑降级生成：

• 变更内容描述：变更了什么，涉及哪些功能模块
• 变更原因（可选）：为什么需要变更
• 预期影响范围（可选）：变更可能影响的模块或系统

执行日志

{
  "execution_id": "exec_p2_xxx",
  "pipeline": "change-impact-analysis",
  "change_id": "CR_2024_001",
  "started_at": "ISO8601",
  "completed_at": "ISO8601",
  "steps": [
    {"step": "step_1_classification", "status": "completed", "duration_ms": 500},
    {"step": "step_2_impact_analysis", "status": "completed", "duration_ms": 2000},
    {"step": "step_3_review_decision", "status": "completed", "duration_ms": 800},
    {"step": "step_4_version_updates", "status": "completed", "duration_ms": 600}
  ],
  "output_ref": "output_ref_xxx",
  "quality_checks_passed": true
}

变更记录

• v2.0: 初始版本
• v2.1: 修复输出校验规则——替换与实际Schema不匹配的review_result字段，对齐output_id/change_id/classification/impact_analysis/review_needed/review_decision/version_updates/summary；修复上游变更响应——对齐变更影响分析场景而非代码审查场景；修复下游通知机制——对齐实际通知场景并新增版本规划调整通知