skills.rest
Rinzler78
Rinzler78COMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-planning

Generate sprint-status.yaml from epic documents and story inventories.

1|Updated Dec 22, 2022
Search Tags:#project management#epics#sprint planning#story tracking#status validation#yaml generation
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-sprint-planning-rinzler78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-sprint-planning-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual effort of building and maintaining sprint tracking from epic files, so teams can keep development status accurate and complete.

Core Features & Use Cases

  • Epic and Story Discovery: Scans epic documents to find every epic, story, and retrospective entry.
  • Status File Generation: Produces a complete sprint-status.yaml with the correct ordering and default states.
  • Status Preservation and Validation: Detects existing story files and preserves more advanced statuses while checking for missing or invalid items.
  • Use Case: Use this Skill when a project needs a fresh sprint plan after epic updates, new story creation, or a status refresh before reporting progress.

Quick Start

Ask the agent to run sprint planning on the repository’s epic files and generate an updated sprint-status.yaml.

Frequently Asked Questions about bmad-sprint-planning

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

FAQPage Schema
How do I generate a sprint status YAML from epic documents?▼

Sprint planning from epic documents involves scanning markdown inputs to discover every epic, story, and retrospective entry. The Skill then generates a complete sprint-status.yaml file with correct ordering and default states for tracking.

How does story status preservation work when updating a sprint plan?▼

Story status preservation detects existing story files and retains their advanced statuses during sprint planning. It validates items against legal state transitions to check for missing or invalid entries while keeping current progress intact.

Can I use this sprint planning tool with sharded markdown inputs?▼

Yes, this sprint planning tool works with sharded markdown inputs. It applies planning workflows that need exhaustive coverage of epics, stories, and retrospectives across single or multiple fragmented markdown files.

What is the best way to refresh sprint tracking after epic updates?▼

The best way to refresh sprint tracking after epic updates is to run sprint planning on the repository's epic files. The Skill rebuilds the sprint-status.yaml completely while preserving existing progress and validating legal state transitions.

When do I need to regenerate a sprint status file for project management?▼

You need to regenerate a sprint status file when a project requires a fresh sprint plan after epic updates, new story creation, or a status refresh before reporting progress to ensure development status remains accurate and complete.

Related Skills

Explore More Software Engineering Skills→
enigmaicon-engenigmaicon-eng
1

bmad-sprint-planning

Parse epic markdown files into an ordered sprint-status.yaml inventory.

Community
Intermediate
enigmaicon-engenigmaicon-eng
1

bmad-sprint-status

Summarize sprint progress from sprint-status.yaml and recommend the next workflow step.

Community
Intermediate
anderson-0anderson-0
4

sprint-planning

Generate sprint status tracking from project epic and story files.

Community
Advanced
lorenzogmlorenzogm
15

bmad-sprint-planning

Generate sprint status files from epic files with Python scripts.

Community
Intermediate