verify-sprint

Trace sprint specification requirements through new or modified source files.

60|13|Updated Jan 10, 2026

Search Tags:#quality assurance #debugging #spec compliance #sprint review #code verification #behavioral testing

Ready to run

npx skills add https://github.com/leogodin217/leos_claude_starter --skill verify-sprint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-sprint
Source: https://github.com/leogodin217/leos_claude_starter/tree/main/.claude/skills/verify-sprint
Command: npx skills add https://github.com/leogodin217/leos_claude_starter --skill verify-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guarantees that your implemented code accurately reflects the detailed requirements and algorithms defined in your sprint specifications, catching subtle behavioral bugs that automated tests might miss.

Core Features & Use Cases

Spec-Fidelity Verification: Meticulously traces each requirement from the specification through the code's execution path.
Behavioral Correctness Check: Verifies that the code behaves exactly as described in the spec, not just structurally present.
Use Case: After a /review-sprint passes basic checks, use this Skill to confirm that the complex branching logic for user authentication in your new feature precisely matches the security protocols outlined in the architecture document.

Quick Start

Use the verify-sprint skill to trace the algorithm steps outlined in the current sprint spec against the newly modified source files.

Frequently Asked Questions about verify-sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify that my code matches sprint specifications precisely?▼

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.

What is the best way to check behavioral correctness beyond standard test coverage?▼

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.

When do I need spec-fidelity verification for my source files?▼

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.

Can I trace architecture document requirements through modified code automatically?▼

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.

Does spec compliance checking replace automated debugging and test coverage?▼

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.

Why does my code pass automated tests but fail sprint review spec compliance?▼

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.