up-9-auditing-spec-coverage
Audits whether code and tests realize the specifications and reports without fixing: for one use case, a matrix of every step, alternative flow, business rule, postcondition and linked NFR against code evidence and test evidence, with gaps, drift and the Status the evidence justifies; for the project, the spec dashboard in Markdown (requirements and use cases complete, in progress, not started; per use case code, unit, end-to-end, regression, integrity) generated from Status fields, identifiers in code and tests, and the test report. Use when the user asks whether UC-XXX is fully implemented or tested, which rules lack tests, whether a Status may move to Tested or Done, for specification coverage, progress, a spec dashboard, or drift between code and specs. Not for line coverage, charts, or reviewing the specs themselves.
Pinned to revision aecf4e91025c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/up-9-auditing-spec-coverage/SKILL.md
- skills/up-9-auditing-spec-coverage/references/conventions.md
- skills/up-9-auditing-spec-coverage/references/dashboard-rules.md
- skills/up-9-auditing-spec-coverage/scripts/coverage_matrix.py
- skills/up-9-auditing-spec-coverage/scripts/spec_dashboard.py
- skills/up-9-auditing-spec-coverage/scripts/spec_model.py
- skills/up-9-auditing-spec-coverage/templates/coverage-matrix.md
- skills/up-9-auditing-spec-coverage/templates/spec-dashboard.md
Every link opens the file at its source, pinned to the revision this page describes.