Scrum Master

Break epics into user stories and plan sprint iterations with velocity metrics.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill scrum-master-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Scrum Master
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/bmad/bmm/scrum-master
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill scrum-master-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Scrum Master skill eliminates ad hoc and poorly scoped sprint planning by converting epics and requirements into right-sized user stories, reliable sprint plans, and measurable velocity so teams can deliver predictably.

Core Features & Use Cases

  • Epic decomposition: Break large epics into implementable user stories with acceptance criteria and technical notes.
  • Sprint planning: Estimate story points, allocate capacity, and assemble sprint iterations that match team velocity.
  • Progress tracking & metrics: Produce velocity reports, burndown insights, and capacity calculations for release planning.
  • Story templates & handoff: Create standardized story artifacts ready for developer implementation and track sprint-status in project storage.
  • Use Case: For a Level 2 project with a completed PRD and architecture, generate a two-sprint plan with prioritized stories and a velocity-backed capacity allocation.

Quick Start

Ask the Scrum Master to run sprint planning using your project's PRD and current sprint status.

Frequently Asked Questions about Scrum Master

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

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

To break epics into implementable user stories for sprint planning, decompose large epics into right-sized stories complete with acceptance criteria and technical notes. This ensures engineering teams receive standardized artifacts ready for immediate development.

What's the best way to estimate story points and allocate capacity for a sprint?

The best way to estimate story points and allocate capacity for a sprint is to match planned iterations against your team's historical velocity. This produces measurable capacity calculations and burndown insights that enable predictable delivery.

Can I generate a two-sprint plan if I only have a PRD and architecture documents?

Yes, you can generate a two-sprint plan using a PRD and architecture documents. The process converts these requirements into prioritized stories and a velocity-backed capacity allocation specifically suited for small to medium projects.

How does tracking velocity metrics improve release planning?

Tracking velocity metrics improves release planning by producing burndown insights and capacity calculations from sprint-status data. This eliminates ad hoc scoping and allows teams to assemble iterations that deliver predictably.

Do I need project memory or status files to persist sprint plans?

Yes, you need project memory or status files to persist sprint plans and velocity metrics. Storing this sprint-status data allows the system to track progress across iterations and maintain standardized story artifacts for developer handoff.