bmad-gds-sprint-planning

Generate sprint status documents using the sprint-planning production workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RafaellsAlmeida/lifetrek --skill bmad-gds-sprint-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-gds-sprint-planning
Source: https://github.com/RafaellsAlmeida/lifetrek/tree/main/.agents/skills/bmad-gds-sprint-planning
Command: npx skills add https://github.com/RafaellsAlmeida/lifetrek --skill bmad-gds-sprint-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning teams often struggle to generate consistent, up-to-date sprint status documents across multiple projects. This Skill automates the creation of sprint status reports by following a defined production workflow.

Core Features & Use Cases

  • Automates generation of sprint status documents from the production sprint-planning workflow.
  • Ensures consistent formatting and versioning for stakeholder updates.
  • Use Case: Generate a status file for the current sprint to share with the team and leadership.

Quick Start

Trigger the sprint-planning workflow to generate the current sprint status file.

Frequently Asked Questions about bmad-gds-sprint-planning

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

FAQPage Schema
How do I automate sprint status report generation for agile teams?

Automate sprint status report generation by triggering a defined production workflow that applies a workflow.yaml configuration to generate consistent, up-to-date status documents for stakeholders.

What is the best way to maintain consistent formatting across multiple sprint status documents?

Maintain consistent sprint status documents by using an automated production workflow that applies standardized workflow configuration files to generate uniformly formatted stakeholder updates.

How do I generate a sprint status file for leadership updates?

Generate a sprint status file for leadership by executing the sprint-planning workflow, which automatically produces a versioned status document ready to share with the team and stakeholders.

Does this sprint planning workflow require any prior technical configuration?

The sprint planning workflow requires no external dependencies but loads a core workflow.xml and applies a specific workflow.yaml file as its configuration to generate the status outputs.

Can I use this automated workflow for sprint planning across multiple projects?

Yes, you can use this automated workflow across multiple projects to solve the struggle of generating consistent, up-to-date sprint status documents by applying a standardized production workflow.

Why does my sprint status document formatting vary between different reporting cycles?

Sprint status formatting varies due to manual generation inconsistencies, which this automated workflow resolves by applying a defined workflow.yaml configuration to standardize outputs.