gaia-sprint-close

Automate sprint closure by validating prerequisites, updating status, and archiving artifacts.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-framework --skill gaia-sprint-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-sprint-close
Source: https://github.com/gaiastudio-ai/gaia-framework/tree/main/plugins/gaia/skills/gaia-sprint-close
Command: npx skills add https://github.com/gaiastudio-ai/gaia-framework --skill gaia-sprint-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yq, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the closure of active sprints, ensuring that all necessary documentation and status updates are correctly recorded, thereby maintaining project integrity and reducing manual errors.

Core Features & Use Cases

  • Sprint Closure Automation: Automates the process of marking a sprint as closed, updating status files, and creating sprint archives.
  • Preconditions Validation: Ensures that all prerequisites for sprint closure are met before proceeding, such as the presence of a retrospective document and all stories being marked as done.
  • Lifecycle Event Emission: Emits a lifecycle event to notify the system that the sprint has been closed, allowing for further processing and tracking.

Quick Start

To close the active sprint, run the following command:

/gaia-sprint-close

Frequently Asked Questions about gaia-sprint-close

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

FAQPage Schema
How do I automate sprint closure for my agile development workflow?

Automating sprint closure involves validating prerequisites like completed retrospectives, updating status files, archiving artifacts, and emitting lifecycle events. This reduces manual errors and maintains project integrity.

What prerequisites must be met before closing an active sprint?

Sprint closure requires all stories marked as done and a completed retrospective document. The automation validates these preconditions before proceeding to update status and archive artifacts.

Does the sprint closure automation require specific shell dependencies?

Yes, sprint closure automation requires yq for YAML manipulation and bash for scripting. These dependencies handle configuration parsing and execute the automated validation and archival workflow.

What happens to sprint artifacts when a sprint is closed?

When a sprint closes, the automation archives sprint artifacts, updates status files, and emits a lifecycle event. This notifies the system for further processing and maintains tracking integrity.

Why should I use automated sprint closure instead of manual status updates?

Automated sprint closure maintains project integrity by validating preconditions and consistently archiving artifacts. It reduces manual errors that occur during manual status updates and documentation.