bmad-sprint-planning

Parse epic and story files to generate sprint-status.yaml with inferred statuses.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-sprint-planning-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-sprint-planning
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-sprint-planning-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates epic and story documents into a single, up-to-date sprint status, eliminating manual tracking overhead and reducing misalignment between planning and execution.

Core Features & Use Cases

  • Automatically aggregates epics and stories from planning documents into a structured sprint-status.yaml.
  • Applies status inference rules to elevate items when corresponding story artifacts exist, while preserving higher statuses from manual edits.
  • Provides a clear visibility of progress for product teams, developers, and project managers during sprint planning and reviews.

Quick Start

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

Frequently Asked Questions about bmad-sprint-planning

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

FAQPage Schema
How do I auto-generate sprint status from epic files?

Sprint status inference works by parsing all epic and story planning documents to map epics to stories, automatically elevating statuses when story artifacts exist while preserving any higher statuses from manual edits.

How do I consolidate epics and stories into a single sprint-status.yaml file?

Yes, manual status tracking is preserved during automated aggregation; the inference rules elevate items when corresponding story artifacts exist, but they strictly preserve higher statuses that were already set manually.

Can I use sprint planning automation for project management without manual status tracking?

Running sprint planning analyzes your epic and story files to generate a sprint-status.yaml file, and returns a concise summary containing total item counts and all in-progress items.

What is the best way to track sprint progress from epic and story planning documents?

Sprint planning automation requires your epic and story files to be present; it parses these planning documents to build a complete sprint inventory and generate the sprint-status.yaml at the configured location.