gds-correct-course

Assess change impact on epics, stories, architecture, and UX artifacts.

26|23|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/laraxot/laravelpizza.com --skill gds-correct-course-laraxot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-correct-course
Source: https://github.com/laraxot/laravelpizza.com/tree/main/.github/skills/gds-correct-course
Command: npx skills add https://github.com/laraxot/laravelpizza.com --skill gds-correct-course-laraxot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage significant changes during project execution, ensuring a structured approach to course correction and impact assessment.

Core Features & Use Cases

  • Impact Assessment: Analyze the effect of changes on epics, stories, architecture, and UX artifacts.
  • Change Proposal: Generate a detailed Sprint Change Proposal with rationale and recommendations.
  • Interactive Workflow: Collaboratively navigate the change process with stakeholders.

Quick Start

Use the gds-correct-course skill to initiate a change navigation process for the 'User Authentication' story.

Frequently Asked Questions about gds-correct-course

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

FAQPage Schema
What is a Sprint Change Proposal in agile project management?

A Sprint Change Proposal is a structured document detailing the rationale and recommendations for navigating significant project changes. It assesses impacts on epics, stories, architecture, and UX artifacts to ensure precise course correction during sprint execution.

How do I assess the impact of a major change on my project's architecture?

To assess impact on architecture, you analyze the proposed change against existing epics, stories, and UX artifacts. This structured impact assessment identifies necessary course corrections and produces a detailed Sprint Change Proposal for stakeholders.

When do I need to initiate a change management process for a project story?

You need to initiate change management when a significant project alteration requires comprehensive analysis and course correction. This process is necessary to collaboratively evaluate impacts on epics, architecture, and UX artifacts before execution.

Can I collaboratively navigate course correction with stakeholders during sprint planning?

Yes, you can collaboratively navigate course correction with stakeholders through an interactive workflow. This process assesses change impacts on project architecture and stories, producing a structured Sprint Change Proposal to guide decisions.

What is the best way to manage significant changes during project execution?

The best way to manage significant project changes is through structured impact assessment and course correction. By analyzing effects on stories and architecture, you generate a detailed Sprint Change Proposal with clear rationale and recommendations.

Does this approach to impact assessment work for UX artifacts and epics?

Yes, impact assessment explicitly analyzes the effects of project changes on UX artifacts and epics alongside architecture and stories. This comprehensive analysis ensures the resulting Sprint Change Proposal addresses all affected project management components.