close-sprint

Name: close-sprint
Availability: InStock
Author: Semicolon

Automates sprint closure, velocity calculation, retrospective generation, task migration, and label removal for Iterations.

Updated Dec 11, 2025

Search Tags:#project management #retrospective #GitHub Issues #velocity calculation #Sprint closure #SEMO #task carry-over

Ready to run

npx skills add https://github.com/semicolon-devteam/semo --skill close-sprint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: close-sprint
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/pm/skills/close-sprint
Command: npx skills add https://github.com/semicolon-devteam/semo --skill close-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, gh, jq.

What problem does it solve?

This Skill automates the complex process of closing a Sprint, including aggregating task statistics, calculating velocity, generating a retrospective summary, and managing uncompleted tasks, saving significant time for PMs.

Core Features & Use Cases

Task Aggregation: Summarizes completed and uncompleted tasks within the Sprint.
Velocity Calculation: Determines the team's velocity based on completed workload points.
Retrospective Summary: Generates a structured retrospective template, including "good points" and "areas for improvement".
Task Carry-Over: Automatically moves uncompleted tasks to the next designated Iteration.
Use Case: At the end of a Sprint, you can use "/SEMO:sprint close '11월 4/4'" to automatically finalize the sprint, calculate its velocity, and prepare a draft for the retrospective meeting.

Quick Start

Close a Sprint: "/SEMO:sprint close" Generate retrospective: "회고 작성" Finalize Sprint: "Sprint 마감"

Frequently Asked Questions about close-sprint

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

FAQPage Schema

How do I automate sprint closure and velocity calculation for my team?▼

Sprint closure automation aggregates completed and incomplete tasks, calculates velocity based on workload points, and generates a retrospective summary appended to your Sprint Issue. This eliminates manual tracking and ensures consistent metrics across iterations.

Can I automatically move incomplete tasks to the next sprint iteration?▼

Yes, the sprint closure process automatically migrates uncompleted tasks to your designated next Iteration while removing the sprint-current label, ensuring no work is lost between cycles.

What data does the retrospective summary include?▼

The retrospective summary provides completion metrics, velocity data, a list of migrated tasks, and structured sections for team input on good points and areas for improvement, formatted as Markdown in your Sprint Issue.

Does this work with GitHub Issues for sprint management?▼

Yes, the Skill integrates with GitHub Issues to manage Sprint closure, task aggregation, and Iteration tracking using gh and jq for reliable CLI-based automation.

What's required before closing a sprint with this automation?▼

You need Bash, the GitHub CLI (gh), and jq installed; tasks must be tagged with iteration labels and story points, and your Sprint Issue must be accessible via GitHub.

Can I customize the retrospective template for my team's format?▼

The Skill generates a standardized retrospective template with completion metrics and velocity; customization of the template structure would require modifying the Skill's implementation logic.