gds-sprint-planning

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

1|Updated Aug 3, 2025

Search Tags:#automation #workflow #epics #yaml #project-management #sprint-planning

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill gds-sprint-planning

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically converts epic/story markdown definitions into a live sprint-status tracker to streamline planning and progress visibility.

Core Features & Use Cases

Generate a complete sprint-status.yaml from markdown epics and stories.
Detect current statuses from the filesystem and preserve higher statuses when needed.
Support both whole-epic documents and sharded epic indexes for flexible workflows.

Quick Start

Run the sprint planning workflow to generate the sprint-status.yaml from your epic files.

Frequently Asked Questions about gds-sprint-planning

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

FAQPage Schema

How do I automatically generate a sprint plan from markdown epic files?▼

To generate a sprint plan from markdown epic files, run a workflow that reads epic and story structures to produce a complete sprint-status.yaml. It detects current progress using filesystem evidence and preserves higher statuses when present.

Can I track sprint progress automatically using a YAML status file?▼

Yes, you can track sprint progress automatically by generating a sprint-status.yaml file. This machine-readable file documents story statuses by reading epic markdown definitions and detecting existing filesystem evidence.

How does sprint planning automation detect the current status of stories?▼

Sprint planning automation detects story statuses by examining filesystem evidence. It reads epic and story markdown structures, identifies existing progress markers, and preserves the highest statuses already present in the project.

Does sprint planning workflow support sharded epic indexes or only whole documents?▼

Sprint planning workflow supports both whole-epic markdown documents and optional sharded epic indexes. This flexible approach allows it to read epic and story structures regardless of how your project files are organized.

What format does the automated sprint tracker output?▼

The automated sprint tracker outputs a machine-readable sprint-status.yaml file. It includes a detailed workflow header and documents the detected statuses of all epics and stories from your markdown project files.

Do I need external dependencies to generate a sprint-status.yaml from epics?▼

No external dependencies are required to generate a sprint-status.yaml from epics. The workflow operates directly on your existing markdown epic and story files, requiring no additional components to parse and track progress.