Free for Scrum Masters
AI skills for the work a Scrum Master does every sprint. Each one teaches your AI assistant how to help with one job: plan a Sprint Review, run a pre-mortem, prep PI Planning, handle a conflict.
Works in Claude, GitHub Copilot, ChatGPT, Gemini and any other assistant. Copy one, download one, or install them all with one command.
A skill for every event
And across the Planning Interval in SAFe
Step by step
A skill is a short instruction file, called SKILL.md, that teaches an assistant how to do one job. Pick your tool:
Don't see Skills in Settings? Your plan may not include them, or on a Team or Enterprise plan an admin may need to turn them on.
On a Mac or Linux terminal, this installs every core skill into Claude Code. Add --target zip, --target copilot or --target plain at the end for the other tools.
curl -fsSL https://raw.githubusercontent.com/dstevenson1981/scrum-master-skills/main/tools/install_library.py | python3 -The library
Each card has a prompt to try it with. Use a made-up team when you practice, never real names or company data.
Sprint Planning: goal, real capacity, commit vs stretch, dependencies, risks, Definition of Done
Needs: Nothing (optional plan audit needs Python 3)
“Plan Sprint 4: 2 weeks, 6 developers, one on leave Thursday and Friday. Our last three velocities were 21, 18 and 24.”
borghei/Claude-Skills · MIT + Commons Clause
Daily Scrum: formats, keeping it to 15 minutes, a quick Sprint Goal check
Needs: Nothing
“Our daily standup has turned into a 40-minute status report to our manager. How do I fix it?”
Agile36 · CC BY 4.0 · source
Sprint Review: agenda, showing the Increment, getting real stakeholder feedback
Needs: Nothing
“Plan a 60-minute Sprint Review. Two of five items are Done and our stakeholders usually skip it.”
Agile36 · CC BY 4.0 · source
Sprint Retrospective: pick a format, facilitate it, make actions stick
Needs: Nothing
“The same three complaints come up every retro and nothing changes. Plan our next retro.”
Agile36 · CC BY 4.0 · source
Backlog Refinement: INVEST checks, vertical splits, Definition of Ready
Needs: Nothing (optional scorer needs Python 3)
“Refine this story: 'As an admin I want a reporting dashboard so I can see everything.'”
borghei/Claude-Skills · MIT + Commons Clause
Scrum of Scrums: coordinate 2-5 teams on one product
Needs: Nothing
“We have 3 teams on one mobile app and they keep breaking each other's releases. How do I set up a Scrum of Scrums?”
skills-on-ai/skills-on-ai · none stated
Retro data pack from git history: velocity, cycle time, churn hotspots
Needs: Python 3 + a git repository
“(inside a git repo) Build a retro data pack for the last two weeks.”
borghei/Claude-Skills · MIT + Commons Clause
Prepare a team for PI Planning: capacity, PI objectives, dependencies, ROAM, confidence vote
Needs: Nothing
“PI Planning is in two weeks and it's my team's first. What do we need ready?”
Agile36 · CC BY 4.0 · source
Coach Sync, PO Sync and ART Sync: what to bring and how to stop status-meeting drift
Needs: Nothing
“Our ART Sync has turned into a 90-minute status meeting. How do I fix it, and what should I bring?”
Agile36 · CC BY 4.0 · source
Inspect and Adapt: PI System Demo, predictability, problem-solving workshop
Needs: Nothing
“Our team planned 40 business value points and achieved 29. Calculate our predictability and prep the problem-solving workshop.”
Agile36 · CC BY 4.0 · source
The Scrum Master role: stances, servant leadership, anti-patterns, onboarding, health check
Needs: Nothing
“I'm joining a new team as Scrum Master next week. What should my first two weeks look like?”
byersboi/claude-agile-skills · none stated
Agile coaching: framework choice, maturity assessment, transformation roadmap
Needs: Nothing (optional scorers need Python 3)
“Our org runs 'Scrum' but nothing has changed in a year. Assess our maturity and suggest a 90-day coaching plan.”
borghei/Claude-Skills · MIT + Commons Clause
Diagnose a recurring problem before fixing it: problem statement, verified root causes
Needs: A project folder (keeps notes)
“Our team misses its Sprint Goal almost every sprint and nobody agrees why. Help me diagnose it.”
Hieu T. Luu · MIT (Hieu T. Luu) · source
Scrum Master of record: runs a team's sprints with memory across sessions
Needs: A project folder (keeps notes in _project/scrum-master/)
“Adopt this team: 'Mobile Squad', 2-week sprints. Set up the workspace.”
Hieu T. Luu · MIT (Hieu T. Luu) · Python tools in the .zip · source
Team chartering: purpose, working agreements and a first Definition of Done
Needs: Nothing
“We're a brand-new team of 7 starting Monday. Plan a 90-minute chartering session.”
Agile36 · CC BY 4.0 · source
Coach through conflict between team members, with the PO or a manager; scripts the conversation
Needs: Nothing
“Two senior developers argue in every refinement and the rest of the team goes quiet. How do I handle it?”
Agile36 · CC BY 4.0 · source
Pick and run a technique: 1-2-4-All, 15% Solutions, TRIZ, dot voting, Fist of Five
Needs: Nothing
“The same two people dominate every meeting. Give me a technique for our next refinement.”
Agile36 · CC BY 4.0 · source
Run a squad health check or psychological safety pulse and turn it into one experiment
Needs: Nothing
“Morale feels low since the reorg. Help me run a health check with my team.”
Agile36 · CC BY 4.0 · source
Run events well for remote and hybrid teams: setup, tools, time zones, engagement
Needs: Nothing
“Half my team is in the office and half is remote, and the remote people never speak. Fix our retro.”
Agile36 · CC BY 4.0 · source
Log, triage and escalate a blocker; draft the escalation message
Needs: Nothing
“We've been blocked 4 days waiting on the platform team for a staging environment. Log it and help me escalate.”
Agile36 · CC BY 4.0 · source
Pre-mortem: imagine the launch failed, surface risks, give each an owner
Needs: Nothing (optional sorter needs Python 3)
“We launch the new checkout in 3 weeks. Run a pre-mortem with me.”
borghei/Claude-Skills · MIT + Commons Clause
Blameless review after an incident, missed launch or failed sprint
Needs: Nothing
“Our release last Friday took the app down for 2 hours. Help me run a blameless post-mortem.”
borghei/Claude-Skills · MIT + Commons Clause
Cross-team dependencies: risk-ranked blocker list and a graph
Needs: Nothing (optional graph tool needs Python 3)
“Three teams depend on each other for the Q3 release. Map the dependencies and show the riskiest ones.”
borghei/Claude-Skills · MIT + Commons Clause
Project risk register (RAID), plans, scope changes, status for delivery
Needs: A project folder (keeps notes in _project/)
“Set up a risk register for our payments migration and add the top five risks.”
Hieu T. Luu · MIT (Hieu T. Luu) · Python tools in the .zip · source
Handle mid-sprint requests and scope creep; draft the reply to the stakeholder
Needs: Nothing
“A VP just asked two of my developers to drop everything for an urgent report. Help me respond.”
Agile36 · CC BY 4.0 · source
Estimation: planning poker, story points, t-shirt sizing, when not to estimate
Needs: Nothing
“One senior developer anchors every estimate. How should I run planning poker?”
Agile36 · CC BY 4.0 · source
Split oversized stories into thin vertical slices
Needs: Nothing
“Split this story: 'Users can pay by card, PayPal or invoice, with refunds.'”
borghei/Claude-Skills · MIT + Commons Clause
User story map: journey, ranked tasks, release lines for an MVP
Needs: Nothing
“Build a story map for a mobile app's first-time onboarding and draw the MVP line.”
borghei/Claude-Skills · MIT + Commons Clause
Write user stories and acceptance criteria, break down epics
Needs: Nothing (optional story generator needs Python 3)
“Write user stories with acceptance criteria for 'customers can save a card for later'.”
Alireza Rezvani · MIT (Alireza Rezvani) · Python tools in the .zip · source
Rank a backlog with RICE, ICE, MoSCoW or weighted scoring
Needs: Nothing (optional scorer needs Python 3)
“Help our Product Owner rank these 8 items with RICE. Ask me for what you need.”
borghei/Claude-Skills · MIT + Commons Clause
Velocity forecasts (Monte Carlo), sprint health score, retro action tracking
Needs: Python 3 + sprint data as JSON (sample included)
“Run a velocity forecast on the sample sprint data and tell me what we can safely commit to next sprint.”
Alireza Rezvani · MIT (Alireza Rezvani) · Python tools in the .zip · source
Flow metrics: lead time, cycle time, throughput, WIP aging, cumulative flow
Needs: Python 3 + an issue status export
“Analyze the sample board data: where is work getting stuck?”
borghei/Claude-Skills · MIT + Commons Clause
Draft and score team OKRs with a counter-metric
Needs: Nothing (optional validator needs Python 3)
“Draft Q1 OKRs for a team whose main problem is slow releases.”
borghei/Claude-Skills · MIT + Commons Clause
Talk leadership out of velocity targets and team comparisons; offer better measures
Needs: Nothing
“My director wants to rank our 4 teams by velocity every month. Prepare me for that conversation.”
Agile36 · CC BY 4.0 · source
Map stakeholders by power, interest and stance; plan engagement
Needs: Nothing (optional analyzer needs Python 3)
“Map the stakeholders for our billing rollout. The finance director is skeptical.”
borghei/Claude-Skills · MIT + Commons Clause
Weekly executive status: highlights, blockers, risks, asks
Needs: Nothing (optional generator needs Python 3)
“Write this week's status update for our sponsor. We're yellow: one blocker, two risks.”
borghei/Claude-Skills · MIT + Commons Clause
Internal updates, newsletters, FAQs, incident and leadership notes
Needs: Nothing
“Write a short update to leadership: we're moving from 3-week to 2-week sprints next month.”
Alireza Rezvani · MIT (Alireza Rezvani) · source
Turn notes or a transcript into decisions, owned action items, open questions
Needs: Nothing
“Here are my notes from Sprint Planning. Summarize decisions and action items. [paste notes]”
borghei/Claude-Skills · MIT + Commons Clause
Decision roles (Driver, Approver, Contributor, Informed) for stalled decisions
Needs: Nothing
“Nobody can decide whether we adopt Kanban for our support team. Set up a DACI for it.”
borghei/Claude-Skills · MIT + Commons Clause
Jira boards, workflows, JQL, automation and dashboards; audit a messy board
Needs: Nothing (optional audit tools need Python 3 + a Jira export)
“Write a JQL filter for everything in the current sprint that's been In Progress for more than 3 days.”
borghei/Claude-Skills · MIT + Commons Clause
Multi-team programs: charter, governance, cross-project dependencies, steering reports
Needs: Nothing (optional tools need Python 3)
“We're starting a 4-team program to replace our billing system. Draft the charter and governance cadence.”
borghei/Claude-Skills · MIT + Commons Clause
Quarter planning meetings: kickoff, weekly check-ins, mid-quarter carry/kill/pivot, close retro
Needs: Nothing (optional tools need Python 3)
“Plan the kickoff and weekly check-in rhythm for next quarter's OKRs.”
borghei/Claude-Skills · MIT + Commons Clause
Background reading: roles, artifacts, events, stories, estimation, metrics
Needs: Nothing
“Explain the difference between the Sprint Review and the Retrospective.”
majiayu000/claude-skill-registry-data · none stated
Check any skill for prompt injection, dangerous code or data leaks before installing it
Needs: Python 3
“Audit the skill folder I just downloaded before I install it.”
borghei/Claude-Skills · MIT + Commons Clause
These skills come from Agile36's Scrum Master training, where students also build, test and share skills of their own.
Skills marked Agile36 are written by Agile36 and shared under CC BY 4.0. Skills from other authors keep their own licenses; each card links to its source. Skills that aren't ours to republish link to their author's repository instead of offering a copy.
SAFe is a registered trademark of Scaled Agile, Inc. The SAFe skills describe practice in Agile36's own words.