skills.rest
co-cddo
co-cddoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bmad-sprint-planning

Generate sprint-status.yaml from Markdown epic files and story data.

4|1|Updated Sep 30, 2024
Search Tags:#automation#workflow#epics#yaml#stories#project-management#sprint-planning
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-sprint-planning-co-cddo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/bmm/workflows/4-implementation/bmad-sprint-planning
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-sprint-planning-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning often requires manual aggregation of epics and stories across planning artifacts to build a current status. This skill automates that process by generating a complete sprint-status.yaml from epic markdown files, ensuring consistency and up-to-date tracking.

Core Features & Use Cases

  • Automatic discovery of epics and stories from planning artifacts (epics.md, epic-*.md) and their stories
  • Status detection and preservation: uses file-system artifacts to infer progress without downgrading statuses
  • Deterministic output: produces a structured sprint-status.yaml that can be consumed by CI or project dashboards
  • Use Case: When starting a sprint, run this skill to generate an initial sprint-status.yaml from your current epic descriptions and stories

Quick Start

Run the sprint planning workflow to generate sprint-status.yaml from the epic Markdown 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 automate sprint planning from epic markdown files?▼

Automate sprint planning by consolidating epic and story data from markdown files into a single sprint-status.yaml, ensuring consistent and up-to-date project tracking without manual aggregation.

Can I generate a sprint-status.yaml file from existing project artifacts?▼

Yes, you can generate a sprint-status.yaml file by reading epic markdown files and planning artifacts, deriving story identifiers, and writing structured development_status entries for automated tracking.

Does sprint status generation preserve existing story progress?▼

Sprint status generation preserves existing progress by reading file-system artifacts to infer current status without downgrading any previously recorded development_status entries in the yaml file.

What is the best way to track epic and story progress for CI dashboards?▼

The best way to track epic progress for CI dashboards is producing a deterministic sprint-status.yaml from planning artifacts, which can be directly consumed by CI pipelines or project management dashboards.

How does automated sprint planning infer development status from epics?▼

Automated sprint planning infers development status by discovering epic and story files from planning artifacts, deriving story identifiers, and preserving existing statuses when writing the final yaml output.

Do I need specific planning artifacts to generate sprint status yaml?▼

Yes, you need markdown epic files such as epics.md or epic-*.md and their associated stories, as the workflow reads these planning artifacts to derive story identifiers and populate the yaml file.

Related Skills

Explore More Product & Management Skills→
mol4mol4
1

bmad-sprint-planning

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

Community
Advanced
MazenMradMazenMrad
1

gds-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

Community
Advanced
MarkusonMarkuson

bmad-sprint-planning

Parse epic and story markdown to generate sprint-status.yaml tracking files.

Community
Advanced
anderson-0anderson-0
4

sprint-planning

Generate sprint status tracking from project epic and story files.

Community
Advanced