skills.rest
skyoxu
skyoxuCOMMUNITY
Explore all skills by this author →
GitHub

gds-sprint-planning

Parse epic markdown files to generate and validate sprint-status.yaml.

Updated Nov 6, 2025
Search Tags:#planning#epics#agile#yaml#status#sprint
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-sprint-planning-skyoxu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-planning
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-sprint-planning
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-sprint-planning-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning often requires consolidating progress from scattered epic and story definitions. This skill automates deriving a consolidated sprint status from epic markdown files, producing a ready-to-use sprint-status.yaml to guide execution and reporting.

Core Features & Use Cases

  • Generate epic and story status from planning_artifacts and implementation_artifacts by parsing epic.md files.
  • Automatically create and maintain a complete sprint-status.yaml with ordering epic, stories, and retrospectives, while preserving existing statuses.
  • Validate consistency between epic definitions and the generated sprint plan, and surface actionable insights for team planning.

Quick Start

Parse your project’s epic files and generate sprint-status.yaml with a single instruction: "Generate sprint status from all epics and update sprint-status.yaml."

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 from epic and story markdown files?▼

To generate a sprint status, this skill parses epic and story definitions from planning artifacts to derive current progress, automatically outputting a consolidated sprint-status.yaml file containing project details and a development_status map.

Can I preserve existing development statuses when regenerating a sprint plan?▼

Yes, when regenerating a sprint plan, the tool preserves previously set statuses if higher-priority data exists, ensuring your existing development progress tracking is retained during automated updates.

How do I validate that all epics and stories are represented in my sprint-status.yaml?▼

To validate sprint-status.yaml consistency, the tool performs basic validation to ensure every epic and story from your parsed epic markdown files is accurately represented in the generated development_status map.

How does agile sprint planning handle sharded epic structures?▼

Agile sprint planning handles sharded epic structures by operating across whole and sharded files, reading all relevant epic definitions to derive statuses for epics, stories, and retrospectives for comprehensive tracking.

What is the best way to automate sprint reporting from scattered epic definitions?▼

The best way to automate sprint reporting is parsing scattered epic markdown files to surface current progress, automatically creating a ready-to-use sprint-status.yaml that guides execution and consolidates tracking.

What format does the automated sprint status generator output?▼

The automated sprint status generator outputs a YAML file named sprint-status.yaml, which contains project details, tracking system information, story location, and a complete development_status map.

Related Skills

Explore More Software Engineering Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

Generate sprint-status.yaml from epic and story markdown files.

Official
Advanced
MazenMradMazenMrad
1

gds-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

Community
Advanced
amitmishra-bylddamitmishra-byldd

bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files for Scrum tracking.

Community
Advanced
co-cddoco-cddo
4

bmad-sprint-planning

Generate sprint-status.yaml from Markdown epic files and story data.

Official
Advanced