gds-correct-course

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-correct-course-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-correct-course
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-correct-course
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-correct-course-pastasus

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. This Skill guides a systematic change analysis and produces an actionable Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Works through a six-section checklist covering trigger context, epic impact, artifact conflicts, path-forward options, and handoff planning. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, GDD sections, narrative, architecture, and UI/UX artifacts in incremental or batch review mode. - Scope-Based Handoff: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or PM/Architect accordingly. - Use Case: A developer discovers a technical limitation that invalidates a planned epic. The Skill loads all planning artifacts, evaluates direct adjustment versus rollback versus MVP scope reduction, and writes a dated Sprint Change Proposal document. ## Quick Start Ask the agent to correct course and analyze the impact of the issue discovered in the current sprint story.

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 discovered mid-sprint in a game project?

Run the correct course workflow, which loads your GDD, epics, architecture, and UX documents, then walks through a change analysis checklist. 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 GDD and Epics documents are essential, and the workflow halts if they cannot be found. Architecture, UX design, narrative, tech spec, and project knowledge documents are loaded when available, supporting both whole-file and sharded formats.

What options does the workflow evaluate for resolving a sprint issue?

It evaluates three paths: Direct Adjustment (modifying or adding stories within the current plan), Potential Rollback (reverting completed work), and MVP Review (reducing or redefining scope). Each option gets an effort and risk estimate before a recommendation is made.

Can I review change proposals one at a time instead of all at once?

Yes, the workflow offers an Incremental mode where each edit proposal is presented individually for approve, edit, or skip decisions. A Batch mode presents all proposals together at the end if you prefer a single review pass.

What happens after the Sprint Change Proposal is approved?

The change is classified by scope: Minor changes route to the Developer agent for direct implementation, Moderate changes go to Product Owner and Developer for backlog reorganization, and Major changes escalate to the Product Manager or Solution Architect for replanning.