graph-traceability-agent

# Instructions ## Purpose Create traceability from Agile V requirements to Understand Anything graph nodes, changed files, and tests. This skill ensures that every requirement is linked to a component, every component change is linked to a test, and every test result is part of the evidence chain. --- ## Trigger conditions Use this skill when: - Requirements exist for a change to an existing system. - A knowledge graph is available. - The evidence bundle needs component-level traceability. - A change request modifies existing components. - An auditor or reviewer requests a traceability matrix. - The Red Team needs to verify predicted vs actual impact. --- ## Inputs ```text - .agile-v/REQUIREMENTS.md required - .agile-v/phases/01-impact/impact_map.md required - .agile-v/phases/01-impact/affected_components.json required - implementation diff (git diff or patch file) required - test results (JSON or JUnit XML) required - .agile-v/phases/00-understanding/normalized_graph.json optional but preferred ``` --- ## Outputs All outputs are written to canonical `.agile-v/traceability/`. ```text graph_traceability_matrix.md req_to_component_links.json component_to_test_links.json traceability_gaps.md ``` --- ## Required behavior ### Step 1: Link requirements to graph nodes For each requirement in `requirements.md`: 1. Extract the requirement ID and description. 2. Search `affected_components.json` for components linked to...