trw-sprint-finish

Automate sprint closure by validating deliverables, updating PRD statuses, archiving sprint documents, and executing the delivery ceremony to ensure rigorous end-to-end completion.

Handle partial sprint completion by validating exit criteria and wave checkpoints, allowing the workflow to process incomplete items while still archiving artifacts and generating retrospective reports.

Verify build gate and exit criteria by spawning adversarial auditors that check PRD completion, perform audits, and enforce wave checkpoints before allowing final artifact movement and delivery.

Yes, the sprint closure workflow operates independently with no external dependencies or components, managing PRD status checks, build gates, and artifact archiving entirely within its internal logic.

Yes, you can update PRD statuses and archive sprint docs automatically by triggering the closure workflow, which locates the active sprint, verifies completion, and moves artifacts to their final state.

Use an automated delivery ceremony for sprint reporting when you need comprehensive retrospective data, requiring validated exit criteria, build gate checks, and archived artifacts to ensure accurate delivery documentation.