skills.rest
Asygnuz-S-A-S
Asygnuz-S-A-SOFFICIAL
Explore all skills by this author →
GitHub

bmad-sprint-status

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

Updated May 22, 2026
Search Tags:#workflow#agile#yaml#story tracking#bmad#sprint status#risk detection
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-sprint-status-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-sprint-status
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-sprint-status-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams tracking epics and stories in a sprint-status.yaml file lack quick visibility into progress, stale data, and risks, making it hard to decide which workflow to run next. ## Core Features & Use Cases - Sprint Summarization: Parses sprint-status.yaml to count story, epic, and retrospective statuses and display a consolidated summary. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with correction prompts. - Next-Action Recommendation: Prioritizes the next workflow (dev-story, code-review, create-story, or retrospective) based on current statuses, with data and validate modes for programmatic use. - Use Case: A developer asks for the sprint status mid-iteration; the skill reports that two stories are in review, recommends running code-review on the first one, and warns that the status file is over seven days old. ## Quick Start Ask the assistant to check the sprint status and show the recommended next workflow for the current project.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I check sprint status from a YAML tracking file?▼

Run the sprint status workflow, which reads sprint-status.yaml from the implementation artifacts directory, parses story and epic statuses, and displays a summary with counts, risks, and a recommended next workflow.

How does the skill decide which workflow to run next?▼

It follows a priority order: in-progress stories trigger dev-story, review stories trigger code-review, ready-for-dev stories trigger dev-story, backlog stories trigger create-story, and optional retrospectives trigger retrospective.

What happens if sprint-status.yaml contains invalid status values?▼

The workflow lists each unrecognized status with its valid options and prompts for corrections, which it writes back to the file before re-parsing. In validate mode it returns is_valid false with the invalid entries.

Can sprint status be consumed programmatically by other workflows?▼

Yes, data mode returns structured outputs such as next_workflow_id, next_story_id, status counts, and risks, while validate mode returns is_valid with error details for file integrity checks.

What risks does sprint status tracking detect?▼

It detects stale files older than seven days, orphaned stories without a matching epic, in-progress epics with no stories, and situations where review or ready-for-dev queues need attention.

Related Skills

Explore More Software Engineering Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

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

Official
Advanced
ravensorbravensorb

l3io-pm-sprint-execute

Orchestrate sprint lifecycle stages with BMad subagents and quality gates.

Community
Advanced
thuantan2060thuantan2060

bmad-customize

Generate project-local TOML override files for BMad agents and workflows.

Community
Advanced
shakhovskiya-createshakhovskiya-create

tracker-integration

Synchronize sprint tasks with Jira, Linear, GitHub Issues, and Shortcut.

Community
Advanced