sprint-reviewer

Analyze sprint execution data and generate per-task verdicts with retro recommendations.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ynitto/sandbox --skill sprint-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-reviewer
Source: https://github.com/ynitto/sandbox/tree/main/.github/skills/sprint-reviewer
Command: npx skills add https://github.com/ynitto/sandbox --skill sprint-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reads sprint execution data to provide objective completion judgments and actionable retrospective guidance without modifying any artifacts.

Core Features & Use Cases

  • Read-only analysis: Evaluates the scrum-master results against done_criteria to determine task status.
  • Objective verdicts & retro input: Generates per-task verdicts (OK, PARTIAL, NG, SKIP) and offers process improvement recommendations.
  • Structured outputs: Produces a consistent review payload ready for downstream planning and reporting.

Quick Start

Provide the sprint goal, sprint number, and the list of tasks with action, done_criteria, status, and result to receive a structured sprint review.

Frequently Asked Questions about sprint-reviewer

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

FAQPage Schema
How do I generate an objective sprint review for my Scrum project?

To generate an objective sprint review, provide the sprint goal, sprint number, and tasks with action, done_criteria, status, and result. The Skill evaluates this data against completion criteria to produce a structured review with per-task verdicts and goal progress.

What is a read-only sprint retrospective analysis?

A read-only sprint retrospective analysis evaluates sprint execution data to provide objective completion judgments and process improvement recommendations without modifying any project artifacts or tasks.

How do I evaluate sprint task completion status against done criteria?

You evaluate sprint task completion by submitting task data containing action, done_criteria, status, and result fields. The analysis compares actual results against defined criteria to output per-task verdicts like OK, PARTIAL, NG, or SKIP.

Can I use this for sprint reviews of varying sizes and complexities?

Yes, this applies to Scrum sprints of varying sizes. It analyzes sprint execution data regardless of scale, producing a consistent structured review payload with per-task verdicts, goal progress, retro input, and identified impediments.

What structured output format does the sprint review payload include?

The sprint review payload includes structured outputs with per-task verdicts, overall goal progress, retrospective recommendations, and identified impediments, making it ready for downstream planning and reporting workflows.

Why does my sprint review need task fields like action and done_criteria?

Task fields like action and done_criteria are required because the review process evaluates actual task results against these specific completion criteria to determine objective status verdicts and generate actionable retrospective guidance.