sprint-review

Automates post-sprint validation of tickets, tests, git state, and architecture.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill sprint-review-busboom-software-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-review
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/sprint-review
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill sprint-review-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-sprint validation ensures all process requirements are met before closing a sprint.

Core Features & Use Cases

  • Ticket Completion Checks: verifies all tickets in the sprint have status: done in frontmatter and are located under tickets/done/.
  • Test & Architecture Validation: ensures full test suite passes and architecture documents reflect the end-of-sprint state.
  • Git & Documentation Compliance: confirms all sprint changes are committed with proper messages and sprint documentation is complete.

Quick Start

Provide the sprint ID and path to the sprint directory, then run the sprint-review validation to generate a verdict and detailed checklist.

Frequently Asked Questions about sprint-review

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

FAQPage Schema
How do I validate sprint tickets and test suite status after a sprint?

Post-sprint validation checks that all tickets have a done status in frontmatter and are moved to tickets/done/, while also verifying the full test suite passes. This ensures all process requirements are met before closing the sprint.

What does post-sprint validation check for git state and architecture alignment?

Post-sprint validation confirms all sprint changes are committed with proper messages and checks that architecture documents reflect the end-of-sprint state. This read-only workflow ensures git compliance and architecture alignment without modifying files.

When do I need to run a sprint review for software engineering process compliance?

You need a sprint review when closing a sprint that involves multiple tickets and architecture changes. It validates ticket completion, test suite success, git state, and sprint documentation to ensure all process requirements are met.

Can I use a read-only workflow to verify sprint documentation and ticket tracking?

Yes, the sprint review operates as a read-only verification workflow. It confirms sprint documentation is complete and validates frontmatter-based ticket states without modifying your repository or sprint artifacts.

How to check if all sprint tickets have status done in frontmatter?

Run a sprint review validation to automatically verify that every ticket in the sprint directory has status: done in its frontmatter. This ticket completion check ensures all tracked items are properly closed before sprint closure.

Does post-sprint validation require CI tests to pass before checking ticket tracking?

Yes, post-sprint validation ensures the full test suite passes as part of its compliance checks. It combines CI test validation with ticket tracking and git state verification to generate a final verdict and detailed checklist.