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

bmad-sprint-status

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarizes sprint status and surfaces risks to help teams stay aligned and make informed decisions during sprint reviews and planning.

Core Features & Use Cases

  • Automatically aggregates sprint status from sprint-status.yaml for quick visibility
  • Detects risks and suggests next actions to keep the sprint on track
  • Produces a concise status summary suitable for stakeholders and team members

Quick Start

Run the sprint-status workflow to load the sprint-status.yaml and generate the current status, risks, and the recommended next action.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I generate a sprint status report from a YAML file?▼

The skill summarizes sprint status by reading a sprint-status.yaml file, validating development statuses against known values, and producing a concise risk report with recommended next actions.

What fields are required in the sprint-status.yaml file?▼

Required fields include generated, last_updated, project, project_key, tracking_system, and a non-empty development_status section to produce a valid sprint summary and workflow recommendation.

Can I use this for sprint planning and review meetings?▼

Yes, this sprint status reporting applies to Scrum teams, project managers, and product owners during sprint reviews, planning, and status reporting to keep teams aligned and informed.

What is the best way to surface project risks during a Scrum sprint?▼

The best way to surface sprint risks is to run the sprint-status workflow, which detects risks from your sprint-status.yaml data and suggests next actions to keep the sprint on track.

Does the sprint status tool work without a tracking system configured?▼

No, a tracking_system field is required in the sprint-status.yaml file, along with project, project_key, generated, last_updated, and a non-empty development_status section for validation.

Related Skills

Explore More Product & Management Skills→
MazenMradMazenMrad
1

gds-sprint-status

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

Community
Advanced
ImaginerLabsImaginerLabs

bmad-sprint-status

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

Official
Advanced
co-cddoco-cddo
4

bmad-sprint-planning

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

Official
Advanced
anderson-0anderson-0
4

sprint-status

Summarize sprint progress and identify delivery risks from status tracking data.

Community
Advanced