review-spec

To verify test case coverage against Confluence planning documentation, you cross-reference planning docs, scenario MD, and TC JSON to detect gaps. This skill enforces strict alignment rules across multiple phases and outputs a structured report detailing any coverage mismatches or missing requirement mappings.

Checking scenario alignment with policy and spec documents requires mapping requirements directly to scenario MD files. This skill validates that functional lists and flows match the source documentation, providing detailed feedback and improvement suggestions whenever omissions or inconsistencies are discovered.

To ensure confirmed scenario items are formalized into TC JSON, you validate that every scenario line item has a corresponding test case entry. This skill performs TC mapping and consistency verification, outputting a structured report when gaps or mismatches between scenario MD and TC JSON are detected.

Yes, you can find missing requirements between scenario authoring and TC formalization phases. It validates spec adherence across multiple phases, enforcing strict alignment rules to ensure full coverage and traceability between Confluence planning docs, scenario MD, and TC JSON outputs.

To start a spec coverage review, you provide the file paths for your confirmed scenario MD and TC JSON. The review begins immediately, cross-referencing these artifacts against planning documentation to identify gaps, inconsistencies, or missing requirement mappings.