gaia-sprint-status

Render sprint dashboards from sprint-status.yaml via sprint-status-dashboard.sh.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GAIA's sprint-status dashboard automates rendering of sprint progress, replacing manual dashboard assembly with a deterministic textual view. It uses sprint-status.yaml as the source of truth and provides a consistent, readable overview for teams.

Core Features & Use Cases

  • Deterministic rendering of the current sprint dashboard via sprint-status-dashboard.sh.
  • Read-only access to sprint-status.yaml to prevent unintended modifications.
  • GAIA-native replacement for the legacy sprint-status XML engine workflow.
  • Supports production workflows with lifecycle and checkpoint integrations for reliability and auditable state.

Quick Start

Run the sprint-status dashboard formatter to render the current sprint status from sprint-status.yaml.

Frequently Asked Questions about gaia-sprint-status

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

FAQPage Schema
How do I generate a deterministic sprint dashboard from a YAML file?

You can generate a deterministic sprint dashboard by rendering a textual view directly from your sprint-status.yaml file using a bash script. This approach enforces read-only access to the YAML source to prevent unintended modifications during progress tracking.

What is deterministic sprint rendering for release readiness?

Deterministic sprint rendering provides a consistent, readable textual overview of sprint progress. It eliminates manual dashboard assembly by using sprint-status.yaml as the single source of truth for software development workflows like sprint planning and release readiness.

Can I use a bash script to track sprint progress without modifying the source data?

Yes, you can use a bash script to track sprint progress with enforced read-only access to sprint-status.yaml. This ensures the source data remains unchanged while providing a clean, auditable state for your production workflows.

What's the best way to replace a legacy XML sprint status engine with a YAML workflow?

The best way to replace a legacy XML sprint status engine is to adopt a GAIA-native workflow that renders dashboards from sprint-status.yaml. This provides clean error handling and lifecycle integrations while using a modern YAML format.

Why does my sprint dashboard rendering fail with a bash script?

Sprint dashboard rendering fails when the bash script encounters formatting issues in sprint-status.yaml or lacks proper read permissions. The script provides clean error handling to help identify these issues during the deterministic rendering process.