scrum-master

Plans sprints, writes user stories, and facilitates agile ceremonies with MoSCoW prioritization.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill scrum-master-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrum-master
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/scrum-master
Command: npx skills add https://github.com/rhorba/RestoLedger --skill scrum-master-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agile teams and solo developers often struggle to break large features into manageable work, prioritize backlogs consistently, and run effective sprint ceremonies. This Skill provides structured templates and facilitation guidance for the full Scrum workflow, from user stories to retrospectives. ## Core Features & Use Cases - User Story Writing: Generates stories in the standard "As a / I want / So that" format with Given/When/Then acceptance criteria, sized to fit within one day of work. - Sprint Planning & Prioritization: Applies MoSCoW (Must/Should/Could/Won't) prioritization, story point estimation (1-13 scale), and session-sized task batching for 30-60 minute work blocks. - Ceremony Facilitation: Provides agendas and formats for sprint planning, daily standups, sprint reviews, and retrospectives (Start/Stop/Continue, 4Ls, Sailboat) via the ceremonies reference guide. - Use Case: A team lead kicks off a two-week sprint and needs a prioritized backlog with estimated stories, a sprint goal statement, and a retrospective format ready for sprint end. ## Quick Start Ask the assistant to plan a two-week sprint for your feature backlog with MoSCoW prioritization and story point estimates.

Frequently Asked Questions about scrum-master

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

FAQPage Schema
How do I write a user story with acceptance criteria?

Write user stories in the format "As a [user type], I want to [action], so that [benefit]" followed by acceptance criteria in Given/When/Then format. Keep each story small enough to complete in one day; split anything larger.

How do I prioritize a sprint backlog with MoSCoW?

MoSCoW prioritization sorts backlog items into Must (ship breaks without it), Should (important but has workaround), Could (nice to have), and Won't (not this sprint). Commit to sprint scope at roughly your velocity plus or minus 20 percent adjusted for capacity.

What story point scale should I use for estimation?

Use the Fibonacci-style scale where 1 is trivial (config change), 3 is a small CRUD endpoint, 5 is a feature with business logic, 8 is a multi-component feature, and 13 is extra large. Stories above 8 points must be split before sprint planning.

Can I use Scrum ceremonies as a solo developer?

Solo developers should skip formal ceremonies and use lightweight task batching instead, grouping work into 30-60 minute session-sized batches. Small teams can use lightweight standups and retros without the full framework.

When is a user story ready for sprint planning?

A story is ready when it has acceptance criteria, identified dependencies, a story point estimate, UI mockups for interface work, API contracts for backend work, and no open clarifying questions. Target two sprints of ready stories in the backlog at all times.