analyze

Traceability between discovery specs and a tech decomposition plan is checked by extracting requirements, test cases, and implementation steps to build a gap-finding matrix. This cross-artifact analysis tags unresolved items like [UNCOVERED] or [UNTESTED] to enforce alignment before coding begins.

Spec drift is the misalignment between discovered requirements and the technical implementation plan. You identify it by performing a read-only analysis of spec artifacts and the tech decomposition to surface gaps, flagging ambiguities with clear findings for remediation.

Build a traceability matrix by targeting a task directory to extract requirements, test cases, and implementation steps. The system links REQ → TEST → Step, automatically tagging untested or uncovered items to produce structured output for validation.

Yes, this consistency check performs a read-only analysis of spec artifacts and the tech decomposition. It extracts data to surface alignment gaps and produces structured output for review without altering your original files.

[UNCOVERED] and [UNTESTED] tags flag gaps and ambiguities found during cross-artifact consistency checks. They identify requirements lacking implementation steps or test cases, enforcing traceability by highlighting unresolved items for targeted remediation.

Requirements traceability analysis should run after tech decomposition and before coding begins. It catches drift early by validating that the discovered spec accurately aligns with the planned implementation steps and test cases.