MaarkssDN/Birthub-360 / .agents/skills/ai-spec-coverage-mapper
ai-spec-coverage-mapper
VerifiedUse when a spec and a test suite both exist but nobody can say which requirements are covered, before a release sign-off, an audit or planning test effort. Uses an LLM to map existing tests to spec sections, outputs a coverage matrix per spec ID and names the gaps. It does not write new tests.
| File | Kind | Size |
|---|---|---|
| .tessl-plugin/plugin.json | config | 434 B |
| SKILL.md | skill md | 7.1 KB |
| references/continuous-coverage-and-verification.md | markdown | 1.7 KB |
references/continuous-coverage-and-verification.md
View on GitHub# Continuous coverage mapping and LLM-claim verification
Deep reference for the `ai-spec-coverage-mapper` SKILL.md. Consult when
scheduling the mapper on a cadence, or when hardening the report against
LLM-hallucinated coverage claims.
## Run it on a weekly cadence
A single mapping goes stale the moment ACs or tests change. Schedule it
weekly and open an issue with the report:
```yaml
on:
schedule:
- cron: '0 4 * * MON'
jobs:
spec-coverage:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- run: python scripts/ai-coverage.py
- uses: peter-evans/create-issue-from-file@v5
with:
title: 'Spec coverage report - week of ${{ github.event.repository.updated_at }}'
content-filepath: spec-coverage-report.md
```
Filter to the ACs and tests changed since the last run to keep cost and
runtime down - re-mapping the whole codebase every week is slow and
expensive for no new signal.
## Verify the LLM's coverage claims
LLMs may claim a test "covers" an AC when it doesn't. Before trusting a
`full` row:
- **Spot-check the highest-priority ACs manually** - read the named test
and confirm it asserts what the AC requires.
- **Cross-reference with `gherkin-from-stories`'s ATDD mode** (in the qa-bdd
plugin) if the team uses `@AC-X.Y` tags - those tags are the ground
truth the LLM's semantic guess can be checked against.
- **Compare the LLM's claim against the test code in human review** -
the report is a starting point for triage, not an authority.
The mapper reads code; it does not run it. A test that imports cleanly
but throws at runtime can still be classified "covered," so a green
matrix is a prompt to verify, not a sign-off on its own.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |