gds-correct-course

Analyzes sprint change impact across GDD, epics, and architecture to produce a Sprint Change Proposal.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-correct-course-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-correct-course
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-correct-course
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-correct-course-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint in a game development project, teams lack a structured way to assess its impact across the GDD, epics, architecture, and UX artifacts and to decide how to respond. This Skill guides that analysis and produces an actionable Sprint Change Proposal. ## Core Features & Use Cases - Impact Analysis Checklist: Systematically evaluates the triggering issue against epics, GDD, narrative, architecture, and UI/UX documents. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, GDD sections, and architecture components. - Scoped Handoff Routing: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or Product Manager/Architect accordingly. - Use Case: A developer discovers a technical limitation that invalidates a planned epic. The Skill loads all planning artifacts, works through the change navigation checklist, and generates a Sprint Change Proposal with a recommended path forward. ## Quick Start Ask the agent to correct course and propose a sprint change for the issue you just discovered during implementation.

Frequently Asked Questions about gds-correct-course

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

FAQPage Schema
How do I handle a major change during a sprint in game development?

Use the correct course workflow to analyze the triggering issue against your GDD, epics, architecture, and UX documents. It produces a Sprint Change Proposal with impact analysis, a recommended path forward, and a handoff plan.

What documents are required to run a sprint change analysis?

The workflow requires a Game Design Document and epics at minimum, and halts if they are missing. Architecture, UX design, narrative, and tech spec documents are loaded when available to broaden the impact analysis.

What is a Sprint Change Proposal and what does it contain?

A Sprint Change Proposal documents the issue summary, epic and artifact impact analysis, the recommended path forward with rationale, detailed before/after edit proposals, and an implementation handoff plan routed by change scope.

When should I use correct course instead of just editing stories directly?

Use it for significant changes affecting project direction, such as invalidated epics, MVP scope questions, or architecture conflicts. Minor story tweaks that do not affect other artifacts can be handled directly without the full checklist.

How does the workflow decide who implements the approved changes?

It classifies the change scope as Minor, Moderate, or Major. Minor changes route to the Developer agent, Moderate changes to Product Owner and Developer for backlog reorganization, and Major changes escalate to Product Manager and Solution Architect.