bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files with status tracking.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-sprint-planning-ahmedkaram50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/bmm/workflows/4-implementation/bmad-sprint-planning
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-sprint-planning-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning can be tedious and error-prone when translating epics into actionable statuses. This Skill automates generating a sprint-status structure from epics to streamline tracking.

Core Features & Use Cases

  • Parse epic files to extract epics and stories
  • Build a complete sprint-status.yaml with statuses for epics, stories, and retrospectives
  • Preserve and merge existing statuses to avoid regression
  • Use when coordinating cross-team development and needing up-to-date progress

Quick Start

Instruct the Skill to generate a sprint plan from the current Epic files to create 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 sprint status tracking from epic markdown files?

You can generate sprint status tracking by parsing epic markdown files to extract stories and building a sprint-status.yaml file. This automates status detection and backlog management across cross-team development projects.

What is the best way to automate sprint planning from epics and stories?

The best way to automate sprint planning is by parsing epic markdown files to build a development_status mapping. This generates a complete sprint-status.yaml file containing epic, story, and retrospective statuses to streamline tracking.

How does sprint-status.yaml preserve existing statuses during backlog updates?

Sprint-status.yaml preserves existing statuses by retaining higher development statuses from the current file during updates. This prevents regression when parsing new epic markdown files and writing the updated sprint plan.

Can I use this sprint planning approach for cross-team development tracking?

Yes, this approach supports cross-team development tracking. It applies to projects with multiple epics and stories, enabling status detection, backlog management, and retrospective planning across teams within an updated YAML file.

Do I need existing sprint-status.yaml to generate a sprint plan?

No, you do not need an existing sprint-status.yaml to generate a sprint plan. The tool builds a complete structure from epic markdown files, but will preserve and merge higher statuses if an existing YAML file is present.