ai-spec-coverage-mapperlisted
Install: claude install-skill testland/qa-skills
# ai-spec-coverage-mapper
## Overview
Coverage tools (per `lcov-analysis` in the qa-test-reporting plugin)
report which **lines** are tested. They don't report which **spec
sections** are tested.
A spec section like "AC-1.4: Already-applied promo shows 'Already
applied'" might be:
- Covered by a test (good).
- Partially covered (the AC says "Already applied"; the test
asserts "Already used" - semantic drift).
- Not covered.
This skill uses an LLM to map tests to spec sections semantically -
the mapping human coverage tools cannot produce.
## When to use
- The team has a spec doc + a test suite and wants spec-coverage
visibility.
- Before a release sign-off - to answer "which requirements are
actually covered?"
- An audit / compliance review needs spec-test traceability.
- After AC drift - tests written months ago for ACs that have
since changed.
Scope is mapping tests that **already exist** and naming the gaps -
not authoring tests for the gaps (that is `ai-test-generator`).
## How to use
1. Point the mapper at the spec doc + the test globs, and set the
AC-ID extraction pattern.
2. Run the LLM mapper - it reads the spec and the tests and emits, per
AC ID, a coverage tier (`full` / `partial` / `none`) plus the
covering test names.
3. Read the coverage matrix - every `partial` and `none` row is a gap.
4. File one action item per gap (fix the drift, or add the missing
test).
5. Schedule it weekly and verify the LLM's claims - see
[references/cont