skills.rest
mattfuster
mattfusterCOMMUNITY
Explore all skills by this author →
GitHub

sprint-close

Close a sprint by evaluating completion, deciding carryover, and archiving sprint data.

Updated Aug 27, 2026
Search Tags:#retrospective#agile#backlog#archive#sprint#carryover
One-click install
npx skills add https://github.com/mattfuster/aisef-setup --skill sprint-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-close
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/sprint-close
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill sprint-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Close a sprint with a structured, guard-railed procedure that turns sprint wrap-up into an auditable, repeatable process, reducing carryover errors and ensuring proper archiving.

Core Features & Use Cases

  • Read final state from 04-sprints/current-sprint.md and categorize WOs and tasks.
  • Propose explicit carryover decisions (Continue, Return to backlog, Descope) and generate retro data.
  • Archive the sprint board and update backlog statuses to reflect the completed sprint.
  • Use when the user says "close sprint", "sprint retro", "end the sprint", or "archive sprint".

Quick Start

Close sprint by issuing the close sprint command and confirming the plan before archiving.

Frequently Asked Questions about sprint-close

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

FAQPage Schema
How do I close a sprint without losing track of carryover work?▼

To close a sprint without losing carryover work, evaluate task completion and make explicit carryover decisions to continue, return to backlog, or descope unfinished items, ensuring no work is silently moved over.

What is the best way to archive a completed sprint board?▼

The best way to archive a completed sprint board is to finalize the sprint state, generate retrospective data, and transition the board into an archived format while updating the backlog to reflect the completed work.

How do I prepare for an agile sprint retrospective using sprint data?▼

You prepare for an agile sprint retrospective by evaluating sprint completion, categorizing work items, and generating retro data from the finalized sprint state to inform team discussions.

Why should I avoid silent carryovers between sprints?▼

Avoiding silent carryovers ensures that unfinished work is explicitly categorized as continued, returned to the backlog, or descoped, creating an auditable and repeatable sprint wrap-up process.

Can I update my backlog automatically when a sprint ends?▼

Yes, closing a sprint updates backlog statuses automatically to reflect the completed sprint, ensuring planning boards and backlog integration remain accurate across sprint boundaries.

Related Skills

Explore More Product & Management Skills→
semicolon-devteamsemicolon-devteam

assign-to-sprint

Assign GitHub Issues to Sprints in GitHub Projects with capacity checks.

Official
Intermediate
tranhieutttranhieutt
70

sprint-plan

Generate sprint plans and status reports from milestone, capacity, and production context.

Community
Advanced
AhmedKaram50AhmedKaram50

bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files with status tracking.

Community
Intermediate
emcconnellemcconnell

retrospective

Generate structured Markdown retrospectives from sprint plans and git commit history.

Community
Advanced