sprint-review

Name: sprint-review
Availability: InStock
Author: Busboom-Foo

Validate sprint tickets, tests, and process guidelines for closure readiness.

Updated Apr 3, 2026

Search Tags:#workflow #testing #review #tickets #sprint

Ready to run

npx skills add https://github.com/Busboom-Foo/meetupfu --skill sprint-review-busboom-foo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-review
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/sprint-review
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill sprint-review-busboom-foo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-sprint validation and governance to ensure readiness for sprint closure by verifying all work items are complete, tests pass, and process rules were followed.

Core Features & Use Cases

Ticket-level validation: ensures every ticket in the sprint has status: done in frontmatter and resides in tickets/done.
Test and architecture alignment: checks that all acceptance criteria are marked completed and architecture/documentation reflect the sprint state.
Safe closure workflow: provides a clear pass/fail verdict and recommended next steps for unaddressed items.

Quick Start

Run a sprint review pass against the current sprint directory to produce a verdict and a 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 readiness before closing a sprint?▼

Sprint readiness validation ensures every ticket has status: done in frontmatter, resides in tickets/done, passes tests, and updates architecture docs before closure.

What is checked during a sprint review for software projects?▼

A sprint review checks ticket status, test coverage, acceptance criteria completion, architecture documentation updates, and commit discipline across sprint branches to produce a pass/fail verdict.

How do I verify all sprint tickets are completed and ready for closure?▼

To verify sprint tickets are completed, check that each ticket has status: done in its frontmatter, is located under tickets/done, and has all acceptance criteria marked with - [x].

Does sprint review require architecture docs to be updated before closure?▼

Yes, sprint review requires architecture documentation to be updated to reflect the sprint state, ensuring technical docs align with completed work before generating a final closure verdict.

What happens if acceptance criteria are not marked complete during sprint validation?▼

If acceptance criteria are not marked with - [x], sprint validation fails the readiness check, providing a detailed checklist and recommended next steps for unaddressed items.

Can I use sprint review for projects without sprint branches?▼

Sprint review applies to software projects closing a sprint and requires commits on the sprint branch, making it unsuitable for workflows lacking dedicated sprint branches or ticket directories.