skills.rest
PastaSus
PastaSusCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gds-sprint-planning

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

1|Updated Sep 18, 2026
Search Tags:#epics#agile#yaml#sprint planning#user stories#backlog#status tracking
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-sprint-planning-pastasus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-sprint-planning
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-sprint-planning
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-sprint-planning-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually maintaining sprint status tracking across epics and stories is error-prone and quickly drifts out of sync with actual development progress. This Skill automates the creation and refresh of a sprint-status.yaml file by parsing epic documents and detecting story file states. ## Core Features & Use Cases - Epic and Story Parsing: Scans epic markdown files (whole or sharded) to extract all epics, stories, and retrospectives into a structured inventory. - Intelligent Status Detection: Upgrades story statuses based on existing story files while preserving more advanced statuses, never downgrading progress. - Structured YAML Output: Generates a validated sprint-status.yaml with status state machines for epics, stories, and retrospectives. - Use Case: After writing your product epics, run sprint planning to produce a complete 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 epics?▼

Run the sprint planning workflow, which scans your planning artifacts directory for files matching the epic pattern, extracts all epics and stories, and writes a complete sprint-status.yaml to your implementation artifacts folder.

How does sprint status detection work with story files?▼

The workflow checks whether a story markdown file exists in the story location for each story key. If found, the story status upgrades to at least ready-for-dev, but existing more advanced statuses like done are never downgraded.

Does it support sharded epic documents?▼

Yes, if no whole epic document is found, the workflow looks for an epics/index.md file and reads all listed epic section files. If both whole and sharded versions exist, the whole document takes priority.

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 to in-progress to review to done. Retrospectives toggle between optional and done.

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

Missing stories usually mean the epic files were not discovered, often due to naming mismatches. Verify your epic files match the configured epic pattern in the planning artifacts directory and use recognizable epic and story headers.

Related Skills

Explore More Product & Management Skills→
alirezarezvanialirezarezvani
25.3k

agile-product-owner

Generates INVEST-compliant user stories, acceptance criteria, and sprint plans for Scrum backlog management.

Community
Intermediate
skyoxuskyoxu

bmad-sprint-planning

Parse epic Markdown files and generate a deterministic sprint-status.yaml.

Community
Advanced
bmad-code-orgbmad-code-org
52.5k

bmad-dev-story

Implements agile story files using red-green-refactor cycles and sprint status tracking.

Official
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:jtbd

Draft Job Stories from GitHub and JIRA issue tracker context.

Official
Advanced