diff-evidence-agent

# Instructions ## Purpose Create evidence explaining the actual implementation diff and its relationship to the predicted impact. This skill closes the loop between the pre-change impact prediction and the post-change reality, and is a key input for the Red Team's evidence quality check. --- ## Trigger conditions Use this skill after implementation and before final validation. Specifically: - After the Build Agent has made changes. - After tests have been run. - Before Red Team evidence verification. - When generating the final evidence bundle. - When a reviewer asks "what actually changed vs what was predicted?" --- ## Inputs ```text - implementation diff (git diff HEAD~1 or patch file) required - .agile-v/phases/01-impact/impact_map.md required - .agile-v/phases/01-impact/change_risk_assessment.md required - .agile-v/REQUIREMENTS.md required - .agile-v/traceability/graph_traceability_matrix.md required - test results (JSON or JUnit XML) required - .understand-anything/diff-overlay.json optional ``` --- ## Outputs All outputs are written to `.agile-v/traceability/` (alongside the traceability matrix). ```text diff_impact_report.md risk_delta.md release_impact_summary.md changed_node_list.json ``` --- ## Required behavior ### Step 1: Parse the diff 1. List all files changed, added, and deleted in the implementation diff. 2. For each changed file, extract...