verify-sprint

To verify code matches sprint specifications, trace each requirement from the spec through the source file's execution path to ensure behavioral correctness. This spec-fidelity verification catches subtle logic bugs that standard automated tests might miss.

Behavioral correctness checking involves meticulously tracing requirement algorithms from architecture documents through newly modified code. This deep validation ensures complex branching logic behaves exactly as described, providing verification beyond mechanical structural checks.

You need spec-fidelity verification when validating complex features, such as user authentication security protocols, against architecture documents. Use it after basic sprint reviews pass to confirm modified source files execute the exact algorithms outlined.

Yes, you can trace architecture document requirements by scoping the verification process specifically to new or modified source files. The Skill maps the algorithm steps from the sprint spec directly against the updated code execution paths.

Spec compliance checking does not replace automated debugging or test coverage. It satisfies the need for deep behavioral validation by tracing execution paths, specifically targeting subtle behavioral bugs that automated tests often miss.

Code can pass automated tests but fail spec compliance because tests often check structural presence rather than precise behavioral correctness. Spec-fidelity verification meticulously traces the sprint specification algorithms to catch these subtle execution path discrepancies.