review-sprint

Validate sprint implementations against acceptance criteria and generate engineer feedback.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/project-purupuru/world-purupuru --skill review-sprint-project-purupuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-sprint
Source: https://github.com/project-purupuru/world-purupuru/tree/main/.claude/skills/reviewing-code
Command: npx skills add https://github.com/project-purupuru/world-purupuru --skill review-sprint-project-purupuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates sprint implementations against acceptance criteria to ensure code quality and alignment with project goals.

Core Features & Use Cases

  • Compares engineer-reported sprint status to documented acceptance criteria, sprint plans, and prior feedback.
  • Generates actionable feedback and tracks remediation across sprint-N.
  • Supports documentation and artifact updates (engineer-feedback.md, sprint.md) to reflect outcomes.

Quick Start

Run the sprint review for sprint-N and generate the engineer-feedback.md with a concise pass/fail verdict and recommended changes.

Frequently Asked Questions about review-sprint

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

FAQPage Schema
How do I validate sprint implementations against acceptance criteria?

Sprint validation compares engineer-reported status against documented acceptance criteria to ensure code quality and alignment with project goals. It identifies traceability gaps, checks security, and generates a concise pass/fail verdict with recommended changes.

What is the best way to generate engineer feedback for a sprint review?

Generating engineer feedback involves comparing the sprint status to prior feedback and sprint plans. This process outputs an engineer-feedback.md file containing actionable remediation steps and tracks the outcomes across the sprint.

How does sprint review ensure documentation consistency across grimoires?

Sprint review ensures documentation consistency by validating artifact updates like sprint.md against the implemented code. It aligns documentation across grimoires and loa to maintain strict traceability and reflect actual sprint outcomes.

Can I track remediation steps across multiple sprints?

Yes, you can track remediation across sprints by validating implementations against prior feedback and acceptance criteria. The process generates actionable feedback and updates documentation artifacts to reflect ongoing remediation outcomes.

What security and code quality checks are included in a sprint review?

Sprint reviews include security checks and code quality validation by comparing the implementation against documented acceptance criteria. This ensures traceability, verifies documentation alignment, and identifies areas requiring remediation.