gds-correct-course

Analyze cross-artifact sprint changes and generate a structured Sprint Change Proposal.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-correct-course-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-correct-course
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-correct-course
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-correct-course-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution by analyzing the impact across all project artifacts and producing a structured Sprint Change Proposal to maintain alignment and momentum.

Core Features & Use Cases

  • Cross-artifact impact analysis across GDD, epics, architecture, UX, and narrative artifacts to identify ripple effects.
  • Structured Sprint Change Proposal generation with sections such as Issue Summary, Impact Analysis, Recommended Approach, Detailed Change Proposals, and Implementation Handoff.
  • Interactive, mode-flexible workflow that supports Incremental or Batch processing and routes handoffs to the appropriate roles.
  • Ensures traceability to current backlog, MVP scope, and release planning for scalable change management.

Quick Start

Describe the triggering issue clearly to initiate the Correct Course workflow and generate a Sprint Change Proposal.

Frequently Asked Questions about gds-correct-course

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

FAQPage Schema
How do I manage sprint changes and assess impact across project artifacts?

To manage sprint changes, analyze cross-artifact ripple effects across GDD, epics, architecture, UX, and narrative materials, then generate a structured Sprint Change Proposal to maintain alignment and momentum.

What is a Sprint Change Proposal and when do I need one?

A Sprint Change Proposal is a structured document tracking significant changes during sprint execution. You need one when a triggering issue requires cross-artifact impact assessment, stakeholder handoff, and stepwise implementation planning.

How to coordinate stakeholder handoff for significant backlog changes?

Coordinate stakeholder handoff by generating a proposal with sections for Issue Summary, Impact Analysis, Recommended Approach, Detailed Change Proposals, and Implementation Handoff, routing tasks to appropriate roles.

Does this sprint change management workflow support traceability to MVP scope?

Yes, the workflow ensures traceability by linking change proposals back to the current backlog, MVP scope, and release planning, providing scalable change management for project teams.

Can I process multiple artifact edits in a batch during change management?

Yes, the interactive workflow supports both Incremental and Batch processing modes, allowing you to manage detailed artifact edits, risk assessment, and defined deployment plans flexibly.

What is the best way to document risk assessment for epic and GDD changes?

Document risk assessment by detailing the triggering issue clearly to initiate the workflow, which produces a proposal encompassing risk evaluation and a defined deployment plan for cross-artifact edits.