skills.rest
cedricfarinazzo
cedricfarinazzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agile-13-sprint-closeout

Automate sprint closeout gates with multi-lens validation before retro.

Updated May 16, 2026
Search Tags:#architecture#qa#jira#confluence#code-review#epic-review#sprint-closeout
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-13-sprint-closeout
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agile-13-sprint-closeout
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-sprint-close/skills/agile-13-sprint-closeout
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-13-sprint-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-of-sprint governance by enforcing a three-lens review before sprint closure.

Core Features & Use Cases

  • Engineer lens: smoke and integration validation against the dev stack to ensure the sprint's changes don't regress core flows.
  • Architect lens: aligns delivered code with Vision Doc, PRD, ADR, Roadmap, and epic ACs to prevent drift.
  • Tech Lead lens: performs a deep code review of the sprint diffs to verify invariants, technical debt, and overall quality.

Quick Start

Trigger agile-13-sprint-closeout at sprint end to run engineer, architect, and tech lead reviews and compile a final closeout report.

Frequently Asked Questions about agile-13-sprint-closeout

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

FAQPage Schema
How do I automate sprint closeout and code review before the retrospective?▼

Sprint closeout automation triggers a three-lens review covering engineer, architect, and tech lead validations to compile an audit-ready artifact before the retrospective begins.

What is a three-lens epic review for sprint validation?▼

A three-lens epic review validates sprint deliverables through engineer smoke tests, architect alignment with Confluence docs, and tech lead code reviews to ensure no critical drift.

How do I check delivered code against Confluence PRDs and ADRs during sprint closure?▼

During sprint closure, the architect lens aligns delivered code against Vision Docs, PRDs, ADRs, Roadmaps, and epic acceptance criteria to prevent architectural drift.

Do I need to run a tech debt sweep before initiating sprint closeout?▼

Yes, sprint closeout requires prerequisite steps like the tech debt sweep to run first, ensuring technical debt is addressed before final architect and tech lead reviews.

How does the tech lead lens perform deep code review on sprint diffs?▼

The tech lead lens performs a deep code review of sprint diffs to verify invariants, assess technical debt, and evaluate overall code quality for the final closeout report.

Can sprint closeout flag critical drift for remediation before the retro?▼

Yes, the sprint closeout gate flags any critical drift found during multi-lens validation for immediate remediation, producing an audit-ready artifact before the retrospective.

Related Skills

Explore More Software Engineering Skills→
petekppetekp
42

audit-and-migrate

Audit and migrate technical debt-heavy codebases through phased workflows.

Community
Advanced
Ethical-AI-SyndicateEthical-AI-Syndicate
1

retrospective-action-tracker

Track retrospective action items and detect recurring systemic patterns.

Official
Intermediate
cedricfarinazzocedricfarinazzo

agile-6-create-epics

Create and align Jira Epics from Roadmap and ADR with dependencies.

Community
Intermediate
MINT-IAMINT-IA

mint-review-pr

Automate an 8-pass staff-engineer review of code diffs.

Official
Advanced