review-sprint

Validate sprint implementations against acceptance criteria and quality standards.

1|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/0xHoneyJar/loa-constructs --skill review-sprint-0xhoneyjar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-sprint
Source: https://github.com/0xHoneyJar/loa-constructs/tree/main/.claude/skills/reviewing-code
Command: npx skills add https://github.com/0xHoneyJar/loa-constructs --skill review-sprint-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates rigorous sprint validation to ensure sprint implementations meet defined acceptance criteria and quality standards before deployment.

Core Features & Use Cases

  • Automated validation of sprint tasks against sprint.md acceptance criteria and architecture patterns.
  • Reconciliation with prior feedback and documentation drift, generating actionable engineer-feedback.md when issues are found.
  • Structured evidence collection and grounding, with precise file:line citations and trajectory logs for auditability.

Quick Start

Run a full sprint review for sprint-N using the engineer report and the current repository state.

Frequently Asked Questions about review-sprint

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

FAQPage Schema
How do I automate sprint reviews against acceptance criteria?▼

Automated sprint review validates sprint implementations against sprint.md acceptance criteria and architecture patterns. It enforces structured evidence gathering with file:line citations and outputs an engineer-feedback.md file when changes are required.

What is documentation drift analysis in sprint validation?▼

Documentation drift analysis detects discrepancies between current repository state and documented architecture during sprint validation. It reconciles prior feedback and generates actionable engineer-feedback.md to correct misalignments.

How do I enforce quality gates before deployment?▼

Quality gates are enforced by rigorously validating sprint tasks against defined acceptance criteria and architecture patterns. The process collects precise file:line citations as evidence to ensure engineering standards are met.

Can I reconcile prior sprint feedback with current repository state?▼

Yes, sprint validation reconciles prior feedback with the current repository state. It analyzes documentation drift and architecture alignment, generating an engineer-feedback.md file with actionable corrections when issues are found.

Does sprint review generate audit logs for engineering tasks?▼

Sprint validation generates trajectory logs and structured evidence with precise file:line citations for auditability. These logs document the validation process against acceptance criteria and quality standards.

What's the best way to check architecture alignment in a sprint?▼

Architecture alignment is checked by validating sprint implementations against defined architecture patterns and sprint.md acceptance criteria. Structured evidence is collected with file:line citations to ensure compliance.