gaia-correct-course

Update story files and reconcile sprint-status.yaml via sprint-state.sh.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manage mid-sprint scope changes by ensuring sprint work is driven from the canonical story files and by reconciling sprint-status.yaml via sprint-state.sh. It prevents drift between planning artifacts and live sprint state, and provides a clear, auditable trail for scope changes, priorities, blockers, and resource updates.

Core Features & Use Cases

  • Updates to story files stay as the source of truth, with sprint-state.sh handling reconciliation to sprint-status.yaml.
  • Supports scope changes, priority shifts, blocker resolution, resource changes, and story injections within an ongoing sprint.
  • Native GAIA workflow conversion of the legacy correct-course engine, preserving governance and auditable history.

Quick Start

Provide a story-key and a change-type to apply a mid-sprint course correction and trigger sprint-state reconciliation.

Frequently Asked Questions about gaia-correct-course

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

FAQPage Schema
How do I manage mid-sprint scope changes without losing traceability?

Mid-sprint scope changes are managed by updating the canonical story files first, then routing reconciliation through sprint-state.sh to update sprint-status.yaml and preserve governance traceability.

What is the best way to reconcile sprint-status.yaml after a priority shift?

The best way to reconcile sprint-status.yaml after a priority shift is to apply the change to the story file source of truth and trigger sprint-state.sh for automated sprint status synchronization.

How do I update story files during an active sprint to resolve blockers?

To update story files during an active sprint, provide the story-key and a change-type such as blocker resolution to apply the course correction and trigger sprint-state reconciliation.

Can I inject new stories into an ongoing sprint while maintaining governance?

You can inject new stories into an ongoing sprint by updating the story files and executing sprint-state.sh, which ensures the sprint-status.yaml reflects the change with an auditable governance trail.

Why does sprint planning drift from the live sprint state during scope changes?

Sprint planning drifts from live sprint state when scope or resource changes bypass the canonical story files, which this workflow prevents by enforcing story files as the source of truth for all updates.

Do I need sprint-state.sh to apply resource changes to an ongoing sprint?

You need sprint-state.sh to apply resource changes because it handles the reconciliation between the canonical story files and sprint-status.yaml, ensuring updates maintain an auditable governance history.