test-evidence-review

# Test Evidence Review `/smoke-check` verifies that test files **exist** and **pass**. This skill goes further — it reviews the **quality** of those tests and evidence documents. A test file that exists and passes may still leave critical behaviour uncovered. A manual evidence doc that exists may lack the sign-offs required for closure. **Output:** Summary report (in conversation) + optional `production/qa/evidence-review-[date].md` **When to run:** - Before QA hand-off sign-off (`/team-qa` Phase 5) - On any story where test quality is in question - As part of milestone review for Logic and Integration story quality audit --- ## 1. Parse Arguments **Modes:** - `/test-evidence-review [story-path]` — review a single story's evidence - `/test-evidence-review sprint` — review all stories in the current sprint - `/test-evidence-review [system-name]` — review all stories in an epic/system - No argument — ask which scope: "Single story", "Current sprint", "A system" --- ## 2. Load Stories in Scope Based on the argument: **Single story**: Read the story file directly. Extract: Story Type, Test Evidence section, story slug, system name. **Sprint**: Read the most recently modified file in `production/sprints/`. Extract the list of story file paths from the sprint plan. Read each story file. **System**: Glob `production/epics/[system-name]/story-*.md`. Read each. For each story, collect: - `Type:` field (Logic / Integration / Visual/Feel / UI / Config/Data) - `## Test Evide...