qa-review

# QA Review Audit a user story implementation against its Example Mapping specification. Reads the EM markdown, finds all implementing code in the codebase, then runs two parallel agents — one for functional coverage, one for code review. Produces a single compact report. **This skill only detects issues — it does not fix them.** ## Reference A ready-to-fill EM template is available at `em_template.md` (in this skill's directory). Share it with the user when they need to write a new spec from scratch. ## 1. Parse the EM Spec Read the markdown file at the provided path. Extract a structured summary with these sections: ### What to extract 1. **User Story title** — the first line or heading describing the US 2. **Rules** — each `# Rule N: <title>` block. For each rule, extract: - Rule number and title - Each `## Example N` with its setup/action/outcome narrative (preserve the full text) 3. **Technical Rules** — bullet points under a `# Technical rules` heading (implementation-focused constraints) 4. **User Events** — content under `# User Events` heading: event names, properties, schemas 5. **Check Also items** — bullet points after "Check also" markers (additional rules/constraints, often separated by dashes) 6. **Code References** — all backtick-quoted terms across the entire spec (class names, field names, event names like `ConflictDetector`, `space_created`, `decision`) 7. **Domain Keywords** — key nouns and verbs from rule titles and examples (e.g., "space", ...