Scrum Master
Turn sprint history and ceremony notes into velocity stats, health scores, and forecasts so a solo builder can run Scrum-lite without a separate analytics tool.
Overview
Scrum Master is an agent skill most often used in Build (also Validate and Operate) that analyzes sprint velocity and health dimensions to guide planning and retros for solo and small-team Scrum.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill scrum-masterWhat is this skill?
- Velocity analysis with mean, median, min/max, commitment ratios, and volatility (coefficient of variation)
- Sprint health scoring across commitment reliability, scope stability, blocker resolution, ceremony engagement, and story
- Trend and forecasting outputs with percentile bands (50%, 70%, 85%, 95%) for planned capacity
- Anomaly detection on sprint velocity (outlier sprints with deviation percentages)
- Structured JSON summaries suitable for agent follow-ups (planning adjustments, retro talking points)
- Sprint health model includes dimension scores such as commitment reliability and scope stability with an overall health
- Velocity forecasting exposes four confidence bands: 50%, 70%, 85%, and 95%
- Volatility reporting includes coefficient of variation and a low/medium/high volatility label
Adoption & trust: 660 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are running sprints alone but only have gut feel about velocity, commitment accuracy, and whether blockers or scope churn are quietly wrecking predictability.
Who is it for?
Indie SaaS teams or solo builders running 1–2 week sprints who want JSON-ready metrics before planning or retro without enterprise agile tooling.
Skip if: Large-program SAFe portfolios, teams with no sprint data or story points, or anyone who needs live Jira/Azure DevOps integration rather than agent-side analysis.
When should I use this skill?
You have sprint or velocity data to analyze before planning, during a sprint review, or when retros keep repeating the same delivery surprises.
What do I get? / Deliverables
You get a structured sprint health and velocity report with trends, forecasts, and anomaly flags you can use to right-size the next sprint backlog and retro actions.
- Velocity and commitment analysis JSON
- Sprint health scorecard with dimension grades
- Forecast bands and anomaly list for planning
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build because sprint execution, backlog grooming, and delivery rhythm live in the product-building phase for most indie teams. PM subphase fits backlog, sprint planning, retros, and delivery metrics—the core Scrum Master responsibilities the skill structures.
Where it fits
Split MVP scope into realistic sprint commitments using historical velocity bands before full build.
Right-size the upcoming sprint after reviewing commitment reliability and scope stability scores.
Check whether blocker resolution scores explain slippage on a release sprint.
Use anomaly flags and trend slope in retro to adjust WIP limits and ceremony habits.
How it compares
Use for sprint analytics and health scoring in chat, not as a substitute for a dedicated agile board or PM suite.
Common Questions / FAQ
Who is scrum-master for?
Solo founders and tiny teams who act as their own Scrum Master and want agent-generated velocity, commitment, and health insights from sprint history.
When should I use scrum-master?
During Validate when scoping MVPs into sprint-sized chunks, in Build for sprint planning and mid-sprint checks, and in Operate when iterating release cadence and fixing recurring blockers.
Is scrum-master safe to install?
Review the Security Audits panel on this Prism page and inspect the skill source in your repo before piping real sprint or customer data through an agent.
SKILL.md
READMESKILL.md - Scrum Master
{ "velocity_analysis": { "summary": { "total_sprints": 6, "velocity_stats": { "mean": 20.17, "median": 20.0, "min": 17, "max": 24, "total_points": 121 }, "commitment_analysis": { "average_commitment_ratio": 0.908, "commitment_consistency": 0.179, "sprints_under_committed": 3, "sprints_over_committed": 2 }, "volatility": { "volatility": "low", "coefficient_of_variation": 0.127 } }, "trend_analysis": { "trend": "stable", "confidence": 0.15, "relative_slope": -0.013 }, "forecasting": { "expected_total": 121.0, "forecasted_totals": { "50%": 115, "70%": 125, "85%": 135, "95%": 148 } }, "anomalies": [ { "sprint_number": 5, "velocity": 17, "anomaly_type": "outlier", "deviation_percentage": -15.7 } ] }, "sprint_health": { "overall_score": 78.3, "health_grade": "good", "dimension_scores": { "commitment_reliability": { "score": 96.8, "grade": "excellent" }, "scope_stability": { "score": 54.8, "grade": "poor" }, "blocker_resolution": { "score": 51.7, "grade": "poor" }, "ceremony_engagement": { "score": 92.3, "grade": "excellent" }, "story_completion_distribution": { "score": 93.3, "grade": "excellent" }, "velocity_predictability": { "score": 80.5, "grade": "good" } } }, "retrospective_analysis": { "summary": { "total_retrospectives": 6, "average_duration": 74, "average_attendance": 0.933 }, "action_item_analysis": { "total_action_items": 15, "completion_rate": 0.467, "overdue_rate": 0.533, "priority_analysis": { "high": {"completion_rate": 0.50}, "medium": {"completion_rate": 0.33}, "low": {"completion_rate": 0.67} } }, "theme_analysis": { "recurring_themes": { "process": {"frequency": 1.0, "trend": {"direction": "decreasing"}}, "team_dynamics": {"frequency": 1.0, "trend": {"direction": "increasing"}}, "technical": {"frequency": 0.83, "trend": {"direction": "increasing"}}, "communication": {"frequency": 0.67, "trend": {"direction": "decreasing"}} } }, "improvement_trends": { "team_maturity_score": { "score": 75.6, "level": "performing" }, "improvement_velocity": { "velocity": "moderate", "velocity_score": 0.62 } } }, "interpretation": { "strengths": [ "Excellent commitment reliability - team consistently delivers what they commit to", "High ceremony engagement - team actively participates in scrum events", "Good story completion distribution - stories are finished rather than left partially done", "Low velocity volatility - predictable delivery capability" ], "areas_for_improvement": [ "Scope instability - too much mid-sprint change (22.6% average)", "Blocker resolution time - 4.7 days average is too long", "Action item completion rate - only 46.7% completed", "High overdue rate - 53.3% of action items become overdue" ], "recommended_actions": [ "Strengthen backlog refinement to reduce scope changes", "Implement faster blocker escalation process", "Reduce number of retrospective action items and focus on follow-through", "Create external dependency register to proactively manage blockers" ] } } { "summary": { "total_sprints": 6, "velocity_stats": { "mean": 20.166666666666668, "median": 20.0, "min": 17, "max": 24, "total_points": 121 }, "commitment_analysis": { "average_commitment_ratio": 0.9075307422046552, "commitment