gds-sprint-planning

Generates sprint-status.yaml tracking files by parsing epic and story markdown documents.

Updated May 7, 2026

Search Tags:#game development #epics #agile #yaml #sprint planning #backlog #status tracking

Ready to run

npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-sprint-planning-jgabriellima

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-sprint-planning
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-sprint-planning
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-sprint-planning-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams tracking agile development in markdown files lack a single source of truth for which epics and stories are backlog, in-progress, or done, forcing manual status bookkeeping that drifts out of sync. ## Core Features & Use Cases - Epic and Story Parsing: Scans epic markdown files (whole or sharded) and extracts every epic, story, and retrospective entry into kebab-case keys. - Intelligent Status Detection: Upgrades story status to ready-for-dev when story files exist, while preserving more advanced existing statuses and never downgrading. - Structured YAML Output: Produces a validated sprint-status.yaml with documented status state machines for epics, stories, and retrospectives. - Use Case: After writing epics for a game project, run sprint planning to generate a complete sprint-status.yaml covering all epics, stories, and retrospectives, then re-run it anytime to refresh auto-detected statuses. ## Quick Start Ask the agent to run sprint planning and generate the sprint status file from your epic documents.

Frequently Asked Questions about gds-sprint-planning

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

FAQPage Schema

How do I generate a sprint status file from epic markdown documents?▼

Run the sprint planning workflow, which scans files matching *epic*.md in your planning artifacts directory, extracts all epics and stories, and writes a complete sprint-status.yaml with detected statuses to your implementation artifacts folder.

How does sprint status detection work for stories?▼

The workflow checks whether a story markdown file exists in the stories location; if found, the story status upgrades to at least ready-for-dev. Existing more advanced statuses like in-progress or done are always preserved and never downgraded.

Can it handle sharded epic documents split across multiple files?▼

Yes. If no whole epic document exists, it looks for an epics/index.md, reads the index, then loads every listed epic section file to build complete coverage. Whole documents take priority when both forms exist.

What statuses can epics, stories, and retrospectives have?▼

Epics flow backlog to in-progress to done. Stories flow backlog, ready-for-dev, in-progress, review, then done. Retrospectives toggle between optional and done. All transitions are documented in the generated YAML header.

Why is my sprint-status.yaml missing stories after regeneration?▼

Missing stories usually mean the epic files use nonstandard headers. The workflow expects patterns like '### Story 1.1: Title' to convert into kebab-case keys such as 1-1-title, so verify your epic markdown follows that heading format.