skills.rest
ArchaonHW
ArchaonHWCOMMUNITY
Explore all skills by this author →
GitHub

gds-sprint-planning

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

Updated Mar 14, 2026
Search Tags:#workflow#epics#agile#yaml#sprint planning#backlog#status tracking
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-sprint-planning-archaonhw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-planning
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-sprint-planning
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-sprint-planning-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping sprint tracking in sync with epic documents is tedious and error-prone. This Skill automates the creation of a complete sprint-status.yaml file by scanning epic markdown files, extracting every epic and story, and detecting current development statuses from the file system. ## Core Features & Use Cases - Epic and Story Parsing: Discovers whole or sharded epic documents (e.g., epics.md, epic-1.md) and converts story headers like "Story 1.1: User Authentication" into kebab-case keys such as 1-1-user-authentication. - Intelligent Status Detection: Upgrades stories to ready-for-dev when matching story files exist, and never downgrades existing advanced statuses like done. - Structured YAML Output: Produces a validated sprint-status.yaml with epics, stories, and retrospective entries in canonical order, including status state machine documentation. - Use Case: After drafting epics for a new project, run sprint planning to instantly generate a tracking file that developers and agents update as stories move from backlog to done. ## Quick Start Ask the AI 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 for 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 are story IDs converted into sprint status keys?▼

Story headers like "Story 1.1: User Authentication" are converted by replacing the period with a dash and converting the title to kebab-case, producing the key 1-1-user-authentication used in the YAML file.

Does sprint planning work with sharded epic files?▼

Yes. If no whole epic document is found, the workflow looks for an epics/index.md, reads all listed epic section files, and combines them for complete coverage. Whole documents take priority when both exist.

Will regenerating sprint status overwrite my existing progress?▼

No. A preservation rule ensures existing statuses are never downgraded. If sprint-status.yaml already marks a story as done, re-running the workflow keeps that status even if auto-detection suggests an earlier state.

What statuses can stories and epics have in sprint-status.yaml?▼

Epics flow from backlog to in-progress to done. Stories flow from backlog to ready-for-dev, in-progress, review, and done. Retrospective entries toggle between optional and done.

Related Skills

Explore More Product & Management Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

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

Official
Advanced
Asygnuz-S-A-SAsygnuz-S-A-S

bmad-dev-story

Implements sprint stories from spec files using a red-green-refactor workflow.

Official
Advanced
shakhovskiya-createshakhovskiya-create

retrospective-writer

Generate sprint and task-cycle retrospectives with metrics and action items.

Community
Advanced
TUP-TESIS-LABTUP-TESIS-LAB
1

jira-workflow

Create and synchronize Jira issues from planning documents using jira-cli.

Official
Advanced