skills.rest
MazenMrad
MazenMradCOMMUNITY
Explore all skills by this author →
GitHub

gds-correct-course

Coordinate sprint-level change navigation to produce a Sprint Change Proposal.

1|Updated Aug 3, 2025
Search Tags:#workflow#planning#epics#handoff#sprint#change-management#gdd
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill gds-correct-course
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-correct-course
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-correct-course
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-correct-course

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The sprint change workflow helps teams systematically identify, analyze, and propose changes when a triggering issue arises, reducing chaos and rework.

Core Features & Use Cases

  • Structured sprint change workflow that guides cross-artifact impact analysis across GDD, epics, architecture, and UX
  • Generate a comprehensive Sprint Change Proposal with clear handoff and implementation planning
  • Supports incremental collaboration or batch review to suit team rhythms

Quick Start

Describe the triggering issue and initiate the Correct Course workflow to produce 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 without disrupting the current workflow?▼

To manage sprint changes effectively, you initiate a structured sprint change workflow that systematically identifies and analyzes triggering issues across GDD, epics, architecture, and UX artifacts. This process produces a comprehensive Sprint Change Proposal to reduce chaos and rework.

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

A Sprint Change Proposal is a structured document generated by analyzing the impact of a triggering issue across project artifacts. You need one when a sprint disruption arises to ensure clear handoff, actionable edit proposals, and explicit implementation planning.

How do I assess the impact of a sprint change across multiple project artifacts?▼

You assess cross-artifact impact by running a sprint change workflow that enforces end-to-end analysis across GDD, epics, architecture, and UX artifacts. This ensures all dependencies are evaluated before selecting a recommended path.

Can I review sprint change proposals incrementally with my team or does it require a batch process?▼

You can review sprint change proposals using either incremental collaboration or batch review. The workflow supports both modes to suit different team rhythms while enforcing comprehensive analysis and explicit handoff planning.

What prerequisites do I need before initiating a sprint change workflow?▼

Before initiating a sprint change workflow, your project must have established GDD, Epics, Architecture, and UX artifacts. The workflow relies on these existing artifacts to perform accurate impact assessment and recommend actionable edit proposals.

How do I plan handoffs after deciding on a course correction for my sprint?▼

You plan handoffs by generating a Sprint Change Proposal that includes explicit handoff planning and actionable edit proposals. This ensures the development team receives clear implementation instructions after the sprint change analysis.

Related Skills

Explore More Product & Management Skills→
skyoxuskyoxu

gds-correct-course

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

Community
Advanced
ldk-hubldk-hub

bmad-correct-course

Generate a structured Sprint Change Proposal from sprint-change triggers.

Community
Advanced
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
wahabmalikwahabmalik

bmad-correct-course

Analyze project artifacts and generate a structured sprint change proposal document.

Community
Advanced