gds-correct-course

name	gds-correct-course
description	Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

Correct Course - Sprint Change Management Workflow

Goal: Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.

Your Role: You are a Developer navigating change management. Analyze the triggering issue, assess impact across GDD, epics, architecture, and UX artifacts, and produce an actionable Sprint Change Proposal with clear handoff.

Conventions

• Bare paths (e.g. checklist.md) resolve from the skill root.
• {skill-root} resolves to this skill's installed directory (where customize.toml lives).
• {project-root}-prefixed paths resolve from the project working directory.
• {skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

1. {skill-root}/customize.toml — defaults
2. {project-root}/_bmad/custom/{skill-name}.toml — team overrides
3. {project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/gds/config.yaml and resolve:

• project_name, user_name
• communication_language, document_output_language
• game_dev_experience
• implementation_artifacts
• planning_artifacts
• project_knowledge
• date as system-generated current datetime
• YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}
• Language MUST be tailored to {game_dev_experience}
• Generate all documents in {document_output_language}
• DOCUMENT OUTPUT: Updated epics, stories, or GDD sections. Clear, actionable changes. Game dev experience ({game_dev_experience}) affects conversation style ONLY, not document updates.

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

Paths

• default_output_file = {planning_artifacts}/sprint-change-proposal-{date}.md

Input Files

Input	Path	Load Strategy
GDD	{planning_artifacts}/*gdd*.md (whole) or {planning_artifacts}/*gdd*/*.md (sharded)	FULL_LOAD
Narrative	{planning_artifacts}/*narrative*.md (whole) or {planning_artifacts}/*narrative*/*.md (sharded)	FULL_LOAD
Epics	{planning_artifacts}/*epic*.md (whole) or {planning_artifacts}/*epic*/*.md (sharded)	FULL_LOAD
Architecture	{planning_artifacts}/*architecture*.md (whole) or {planning_artifacts}/*architecture*/*.md (sharded)	FULL_LOAD
UX Design	{planning_artifacts}/*ux*.md (whole) or {planning_artifacts}/*ux*/*.md (sharded)	FULL_LOAD
Tech Spec	{planning_artifacts}/*tech-spec*.md (whole) or {planning_artifacts}/*spec-*.md (whole)	FULL_LOAD
Document Project	{project_knowledge}/index.md (sharded)	INDEX_GUIDED

Context

• Load **/project-context.md if it exists

Execution

Document Discovery - Loading Project Artifacts

Strategy: Course correction needs broad project context to assess change impact accurately. Load all available planning artifacts.

Discovery Process for FULL_LOAD documents (GDD, Narrative, Epics, Architecture, UX Design, Tech Spec):

1. Search for whole document first - Look for files matching the whole-document pattern (e.g., *gdd*.md, *narrative*.md, *epic*.md, *architecture*.md, *ux*.md, *tech-spec*.md)
2. Check for sharded version - If whole document not found, look for a directory with index.md (e.g., gdd/index.md, epics/index.md)
3. If sharded version found:
   • Read index.md to understand the document structure
   • Read ALL section files listed in the index
   • Process the combined content as a single document
4. Priority: If both whole and sharded versions exist, use the whole document

Discovery Process for INDEX_GUIDED documents (Document Project):

1. Search for index file - Look for {project_knowledge}/index.md
2. If found: Read the index to understand available documentation sections
3. Selectively load sections based on relevance to the change being analyzed — do NOT load everything, only sections that relate to the impacted areas
4. This document is optional — skip if {project_knowledge} does not exist (greenfield projects)

Fuzzy matching: Be flexible with document names — users may use variations like gdd.md, game-design-document.md, etc.

Missing documents: Not all documents may exist. GDD and Epics are essential; Architecture, UX Design, Tech Spec, Narrative, and Document Project are loaded if available. HALT if GDD or Epics cannot be found.

Load **/project-context.md for coding standards and project-wide patterns (if exists) Confirm change trigger and gather user description of the issue Ask: "What specific issue or change has been identified that requires navigation?" Verify access to required project documents: - GDD (Game Design Document) - Current Epics and Stories - Architecture documentation - UI/UX specifications - Narrative Design documentation Ask user for mode preference: - **Incremental** (recommended): Refine each edit collaboratively - **Batch**: Present all changes at once for review Store mode selection for use throughout workflow

HALT: "Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why."

HALT: "Need access to project documents (GDD, Epics, Architecture, UI/UX) to assess change impact. Please ensure these documents are accessible."

Read fully and follow the systematic analysis from: checklist.md Work through each checklist section interactively with the user Record status for each checklist item: - [x] Done - Item completed successfully - [N/A] Skip - Item not applicable to this change - [!] Action-needed - Item requires attention or follow-up Maintain running notes of findings and impacts discovered Present checklist progress after each major section

Identify blocking issues and work with user to resolve before continuing

Based on checklist findings, create explicit edit proposals for each identified artifact

For Story changes:

• Show old → new text format

• Include story ID and section being modified

• Provide rationale for each change

• Example format:

  Story: [STORY-123] User Authentication
  Section: Acceptance Criteria
  
  OLD:
  - User can log in with email/password
  
  NEW:
  - User can log in with email/password
  - User can enable 2FA via authenticator app
  
  Rationale: Security requirement identified during implementation
  

For GDD modifications:

• Specify exact sections to update
• Show current content and proposed changes
• Explain impact on MVP scope and requirements

For Narrative Design modifications:

• Specify exact sections to update
• Show current content and proposed changes
• Explain impact on story, character, or world-building consistency

For Architecture changes:

• Identify affected components, patterns, or technology choices
• Describe diagram updates needed
• Note any ripple effects on other components

For UI/UX specification updates:

• Reference specific screens or components
• Show wireframe or flow changes needed
• Connect changes to user experience impact

Present each edit proposal individually Review and refine this change? Options: Approve [a], Edit [e], Skip [s] Iterate on each proposal based on user feedback

Collect all edit proposals and present together at end of step

Compile comprehensive Sprint Change Proposal document with following sections:

Section 1: Issue Summary

• Clear problem statement describing what triggered the change
• Context about when/how the issue was discovered
• Evidence or examples demonstrating the issue

Section 2: Impact Analysis

• Epic Impact: Which epics are affected and how
• Story Impact: Current and future stories requiring changes
• Artifact Conflicts: GDD, Narrative, Architecture, UI/UX documents needing updates
• Technical Impact: Code, infrastructure, or deployment implications

Section 3: Recommended Approach

• Present chosen path forward from checklist evaluation:
  • Direct Adjustment: Modify/add stories within existing plan
  • Potential Rollback: Revert completed work to simplify resolution
  • MVP Review: Reduce scope or modify goals
• Provide clear rationale for recommendation
• Include effort estimate, risk assessment, and timeline impact

Section 4: Detailed Change Proposals

• Include all refined edit proposals from Step 3
• Group by artifact type (Stories, GDD, Narrative, Architecture, UI/UX)
• Ensure each change includes before/after and justification

Section 5: Implementation Handoff

• Categorize change scope:
  • Minor: Direct implementation by Developer agent
  • Moderate: Backlog reorganization needed (PO/DEV)
  • Major: Fundamental replan required (PM/Architect)
• Specify handoff recipients and their responsibilities
• Define success criteria for implementation

Present complete Sprint Change Proposal to user Write Sprint Change Proposal document to {default_output_file} Review complete proposal. Continue [c] or Edit [e]?

Get explicit user approval for complete proposal Do you approve this Sprint Change Proposal for implementation? (yes/no/revise) Gather specific feedback on what needs adjustment Return to appropriate step to address concerns If changes needed to edit proposals If changes needed to overall proposal structure Finalize Sprint Change Proposal document Determine change scope classification:

• Minor: Can be implemented directly by Developer agent
• Moderate: Requires backlog reorganization and PO/DEV coordination
• Major: Needs fundamental replan with PM/Architect involvement

Provide appropriate handoff based on scope:

Route to: Developer agent for direct implementation Deliverables: Finalized edit proposals and implementation tasks Route to: Product Owner / Developer agents Deliverables: Sprint Change Proposal + backlog reorganization plan Route to: Product Manager / Solution Architect Deliverables: Complete Sprint Change Proposal + escalation notice

Confirm handoff completion and next steps with user Document handoff in workflow execution log

Summarize workflow execution: - Issue addressed: {{change_trigger}} - Change scope: {{scope_classification}} - Artifacts modified: {{list_of_artifacts}} - Routed to: {{handoff_recipients}}

Confirm all deliverables produced:

• Sprint Change Proposal document
• Specific edit proposals with before/after
• Implementation handoff plan

Report workflow completion to user with personalized message: "Correct Course workflow complete, {user_name}!" Remind user of success criteria and next steps for Developer agent

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.