skills.rest
Busboom-Foo
Busboom-FooOFFICIAL
Explore all skills by this author →
GitHub

close-sprint

Close a completed sprint by verifying tickets, merging the branch, and archiving data.

Updated Apr 3, 2026
Search Tags:#automation#git#merge#archiving#ci-cd#sprint-management#close-sprint
One-click install
npx skills add https://github.com/Busboom-Foo/meetupfu --skill close-sprint-busboom-foo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-sprint
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/close-sprint
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill close-sprint-busboom-foo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates and closes a completed sprint by verifying that all tickets are done, merging the sprint branch, and archiving sprint documentation.

Core Features & Use Cases

  • Pre-condition checks with stakeholder confirmation to ensure sprint readiness.
  • Automatic merge of sprint branch to main, version tagging, and cleanup of the feature branch.
  • Archiving sprint artifacts and updating the state database to reflect completion.

Quick Start

Close the active sprint by providing the sprint ID and confirming stakeholder approval.

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 closing with a safe Git merge and branch cleanup?▼

To close a sprint, provide the sprint ID and confirm stakeholder approval. The process runs pre-condition checks with self-repair, merges the sprint branch to main, creates a version tag, and cleans up the branch.

What pre-condition checks are needed before merging a sprint branch to main?▼

Pre-condition checks verify that all tickets are completed and stakeholder approval is confirmed. The process applies self-repair mechanisms to ensure sprint readiness before merging and archiving sprint documentation.

Can I use CI-CD automation to archive sprint data and update the state database?▼

Yes, CI-CD automation can archive sprint data and update the state database by using the close_sprint tool. It validates tickets, merges branches, and updates the state database to reflect sprint completion.

Does the sprint archiving workflow require stakeholder confirmation before merging?▼

Sprint archiving requires stakeholder confirmation to ensure sprint readiness. It performs pre-condition checks with self-repair to validate that all tickets are done before merging the sprint branch and archiving artifacts.

What happens to the Git sprint branch after version tagging and sprint completion?▼

After version tagging and sprint completion, the Git sprint branch is cleaned up. The workflow automatically merges the branch to main, creates a version tag, and removes the feature branch to finalize the sprint close.

Related Skills

Explore More Software Engineering Skills→
busboom-software-studiobusboom-software-studio
1

close-sprint

Validate tickets, merge sprint branches, and archive sprint history.

Official
Advanced
ITSaltITSalt
23

nacl-tl-release

Automate end-to-end software releases by merging PRs, validating CI, and publishing changelogs.

Community
Advanced
rnavarychrnavarych
14

role-database:database-devops

Automate database provisioning, Kubernetes deployment, and CI/CD integration with Terraform.

Community
Advanced
nguyennd93nguyennd93

test-evidence-review

Evaluate test file assertion coverage and manual evidence criteria completion.

Community
Intermediate