Scrum Master

Break epics into user stories with acceptance criteria and Fibonacci story points.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/co-cddo/innovation-sandbox-on-aws-deployer --skill scrum-master-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Scrum Master
Source: https://github.com/co-cddo/innovation-sandbox-on-aws-deployer/tree/main/.claude/skills/bmad/bmm/scrum-master
Command: npx skills add https://github.com/co-cddo/innovation-sandbox-on-aws-deployer --skill scrum-master-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaking down large epics into manageable user stories, estimating effort, and planning effective sprints can be challenging. This Skill automates agile planning, ensuring work is properly sized, prioritized, and tracked.

Core Features & Use Cases

  • Sprint Planning: Guides the creation of sprint iterations from epics and requirements, allocating work based on capacity and priority.
  • User Story Creation: Helps define detailed user stories with clear acceptance criteria and assigns story points using a Fibonacci scale.
  • Sprint Progress Tracking: Monitors current sprint status, calculates team velocity, and generates reports.
  • Use Case: After your PRD is complete, use this Skill to plan your first sprint. It will help break down epics into stories, estimate points, and create a sprint plan document, setting your team up for efficient development.

Quick Start

Plan the next sprint for the 'MyApp' project based on the existing PRD. /sprint-planning

Frequently Asked Questions about Scrum Master

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

FAQPage Schema
How do I break down epics into user stories for sprint planning?

Breaking down epics into user stories involves decomposing large requirements into smaller, estimable tasks with clear acceptance criteria. This Skill automates that process by generating detailed user stories sized using Fibonacci story points, ready for sprint allocation based on team velocity and capacity.

What's the best way to estimate story points and plan sprint velocity?

Story point estimation uses relative sizing on a Fibonacci scale to reflect effort and complexity. This Skill assigns points during story creation and calculates team velocity by tracking completed points across sprints, enabling data-driven capacity planning for future iterations.

How do I create an effective sprint plan from a product requirements document?

Effective sprint planning requires decomposing requirements into prioritized stories, estimating effort, and allocating work within team capacity. This Skill automates this workflow by converting epics from your PRD into acceptance-criteria-driven stories and generating a sprint plan document with velocity-based allocation.

Can I track sprint progress and generate reports on team velocity?

Sprint progress tracking monitors current iteration status and measures team velocity—the number of story points completed per sprint. This Skill generates reports on velocity trends and sprint metrics, enabling teams to forecast delivery timelines and optimize capacity planning.

Do I need detailed acceptance criteria for every user story?

Acceptance criteria define when a story is complete and testable. This Skill creates detailed acceptance criteria for each user story during backlog refinement, ensuring clarity for development and QA teams and reducing scope ambiguity during implementation.

What happens after sprint planning—how do I track what's in progress?

After sprint planning, teams execute the sprint while monitoring progress against planned velocity. This Skill tracks current sprint status, calculates actual velocity, and surfaces metrics needed to identify blockers and adjust upcoming sprints accordingly.