skills.rest
marcmontecalvo
marcmontecalvoCOMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-planning

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

Updated Jul 11, 2026
Search Tags:#automation#workflow#planning#epics#sprint#tracking
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-sprint-planning-marcmontecalvo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-sprint-planning-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of maintaining sprint status by automatically parsing epic documentation and synchronizing the state of user stories into a structured tracking file.

Core Features & Use Cases

  • Automated Status Tracking: Detects story statuses and generates a comprehensive sprint-status.yaml file based on epic files.
  • Intelligent State Machine: Enforces a consistent workflow for epics, stories, and retrospectives, ensuring no work item is overlooked.
  • Use Case: When a team finishes a planning session, use this skill to instantly generate a status report that reflects the current progress of all epics and stories across the project.

Quick Start

Ask the assistant to run sprint planning to generate the latest status tracking file from your epic documentation.

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 status tracking from epic documentation?▼

Automate sprint status tracking by parsing epic and story documentation to detect work item statuses and generate a structured sprint-status.yaml file. This eliminates manual overhead by synchronizing user story states into a comprehensive tracking file.

What is the best way to maintain a consistent development state machine for epics and stories?▼

Maintain a consistent development state machine by enforcing a structured workflow for epics, stories, and retrospectives. This ensures no work item is overlooked and keeps sprint tracking synchronized across the entire project.

Do I need Python 3 to generate sprint status tracking files from epics?▼

Yes, Python 3 is required to run the scripts that parse epic documentation and generate sprint status tracking files. You also need access to project-specific configuration files to resolve workflow steps and persistent facts.

Can I instantly generate a sprint status report after a planning session?▼

Yes, you can instantly generate a sprint status report after a planning session by running sprint planning. The skill parses project-wide epic files to detect story statuses and outputs a comprehensive sprint-status.yaml file.

How does automated sprint planning handle project-specific configuration files?▼

Automated sprint planning uses project-specific configuration files to resolve workflow steps and persistent facts. This allows the state machine to accurately detect work item statuses and maintain consistent epic and story tracking.

Related Skills

Explore More Software Engineering Skills→
MarkusonMarkuson

bmad-sprint-planning

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

Community
Advanced
scomofoscomofo

retrospective

Generate sprint or milestone retrospectives from plans, status, and git history.

Community
Advanced
tiweentiween

bmad-sprint-planning

Generate a sprint-status.yaml file from epic files using Python scripts.

Official
Advanced
ImaginerLabsImaginerLabs

bmad-sprint-planning

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

Official
Advanced