| name | cypress-coverage-matrix-auto-sync |
| description | Coverage-maintenance skill for Cypress planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change. |
| metadata | {"author":"jovd83","version":"1.1","dispatcher-category":"testing","dispatcher-capabilities":"coverage-maintenance, cypress-coverage-sync","dispatcher-accepted-intents":"sync_cypress_coverage_artifacts","dispatcher-input-artifacts":"coverage_plan, test_suite, traceability_artifacts","dispatcher-output-artifacts":"updated_coverage_artifacts, sync_report","dispatcher-stack-tags":"cypress, coverage, sync","dispatcher-risk":"low","dispatcher-writes-files":true} |
Telemetry & Logging
[!IMPORTANT]
All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason> (or ./log-dispatch.sh on Linux)
Coverage Matrix Auto-Sync
Use this skill to keep planning artifacts aligned with reality after the suite changes.
1. Traceability Maintenance
Identify added, removed, renamed, or moved scenarios and reconcile them across:
- the coverage plan or matrix,
- narrative TDD or BDD documents,
- implementation references such as
.cy.ts files, titles, tags, or scenario IDs.
Do not invent implementation links that you cannot verify.
2. Coverage Stats Recalculation
Recalculate summary counts only after the underlying scenario rows are correct.
Flag drift explicitly when the plan claims coverage that the implementation cannot prove.
3. Anchor & ID Standards
- Prefer stable scenario IDs over human-readable titles for traceability joins.
- Keep anchors and IDs consistent across plan, docs, and code.
- Ensure each requirement or acceptance-criteria item can be traced to at least one scenario when the matrix is intended to be complete.
4. Documentation Sync Workflow
- Treat
coverage_plan/*.md as the source of truth for planned scope.
- Treat
docs/tests/**/*.md as the narrative traceability layer when those files exist.
- Treat Cypress implementation as the proof layer for executed behavior.
- Report unmapped requirements, stale IDs, broken links, or evidence gaps explicitly.
Checklist
