skills.rest
MazenMrad
MazenMradCOMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-status

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint status is often scattered across artifacts and conversations. This Skill provides a concise, actionable summary of current sprint progress and risk indicators derived from sprint-status.yaml, enabling faster alignment and decision-making.

Core Features & Use Cases

  • Summarizes sprint status by counting stories and epics in each state (backlog, in-progress, done) and surfacing key risks.
  • Recommends next actions based on status patterns (e.g., in-progress, in-review, backlog) to keep the sprint moving.
  • Use Case: A team leads a daily standup and asks for a quick health check; this Skill returns a clear status snapshot plus recommended next steps.

Quick Start

Run the sprint-status workflow on the existing sprint-status.yaml to generate a summary and recommended next actions.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I summarize sprint status and identify risks from a YAML file?▼

The workflow processes sprint-status.yaml by validating required metadata, counting stories and epics in each state such as backlog or in-progress, and surfacing key sprint risks for quick decisions.

What is the best way to generate agile risk signals for daily standups?▼

The best way to generate agile risk signals is running the sprint-status workflow on your YAML file to produce a concise health check snapshot with story counts and recommended next actions for the team.

How does sprint planning reporting work when story states are mixed?▼

When story states are mixed, sprint planning reporting computes totals for states like in-progress and in-review, then recommends the next workflow action based on those status patterns to keep the sprint moving.

Do I need a specific YAML structure to compute sprint status counts?▼

Yes, a structured sprint-status.yaml file with required metadata is needed, because the workflow validates these fields before computing counts of stories and epics across backlog, in-progress, and done states.

Can I use this to recommend next actions for in-progress and in-review stories?▼

Yes, the workflow analyzes status patterns for in-progress and in-review stories in the YAML file, recommending the appropriate next workflow action to maintain sprint momentum and enable quick decisions.

Related Skills

Explore More Software Engineering Skills→
thuantan2060thuantan2060

bmad-sprint-status

Summarizes sprint statuses from sprint-status.yaml and recommends the next BMAD workflow action.

Community
Intermediate
AbsolutelySkilledAbsolutelySkilled
207

user-stories

Generate user stories and acceptance criteria using INVEST and Given/When/Then templates.

Official
Advanced
co-cddoco-cddo
4

bmad-sprint-planning

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

Official
Advanced
aj-geddesaj-geddes
472

Scrum Master

Automate sprint planning and backlog management with YAML-based templates.

Community
Basic