regression-selection-agent

# Instructions ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs. - The system has existing tests that need to be triaged. - The Test Designer needs to know which existing tests to include. - A release gate requires documented regression-test coverage. --- ## Inputs ```text - .agile-v/phases/01-impact/impact_map.md required - .agile-v/phases/01-impact/affected_components.json required - test inventory (discovered from test/ directory or graph test nodes) required - .agile-v/phases/00-understanding/normalized_graph.json optional but preferred - previous test results (if available) optional ``` --- ## Outputs All outputs are written to canonical `.agile-v/phases/03-regression/`. ```text required_regression_tests.md selected_tests.json regression_coverage_rationale.md missing_regression_tests.md ``` --- ## Required behavior ### Step 1: Discover existing tests 1. Search the repository for test files (`.spec.ts`, `.test.ts`, `_test.py`, `test_*.py`, etc.). 2. If a normalized graph is available, use test nodes from the graph. 3. Build a test invento...