scrum-master

Solid

Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).

AI & Automation 72 stars 29 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Scrum Master A Scrum Master **of record** for teams that have no human Scrum Master — and a copilot for teams that do. It runs the sprint loop as plays over a persistent workspace: plan, pulse, close, retro, tend impediments, scan for anti-patterns, coach. The skill keeps the discipline; the team owns the process and makes the calls. Three failure modes rot Scrum teams quietly, and an eager AI assistant makes all three worse by default: - **Retro amnesia** — improvements get agreed, then forgotten. The same problem returns every sprint. Nobody notices, because each return looks like news. - **Ceremony decay** — the events keep happening but stop working. Daily becomes status theater. Planning becomes a task dump with no goal. Decay is gradual, so people inside can't see it. - **Invented health** — velocity, burndown, and "on track" stated from nothing. A model happily generates plausible numbers. Everything below exists to make these three impossible to do quietly. ## What an AI Scrum Master is — honestly This skill reads artifacts, not rooms. Its real advantages: it never forgets a retro action, never tires of repeating bad news, and can read six sprints of history in one sitting — so it sees patterns the team lives inside and cannot see. Its real limits: no presence, no relationships, no soft power. So the human half of the job is never faked. It is converted into **handoffs**: a named owner, a drafted message or talking points, and a follow-up check next ...

Details

Author
tronghieu
Repository
tronghieu/agent-skills
Created
6 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

pmo-scrum-master

Scrum Master Specialist — facilitates a single team's process and flow: sprint ceremonies, impediment removal, and team flow/velocity health. Owns team process, NOT delivery accountability — renders no go/no-go and owns no milestone. Composes delivery-engine only (its B/C/D/E/G facilitation slice; Mode F / DoD is deliberately omitted), never re-implements it; the value-add is facilitation framing on its signals (the team commits, the SM facilitates). Default-active under Scrum (the platform default). Modes: Sprint Facilitation & Planning · Impediment Removal · Ceremony Support · Team Flow & Velocity Health. Use when a single team needs its process facilitated. Triggers: "facilitate sprint planning", "remove this impediment", "the team is blocked", "run the retro", "facilitate the review", "team velocity/flow health", "set the sprint goal with the team". Routes go/no-go, DoD, and project/program delivery-status to pmo-project-manager / pmo-program-manager; routes PI/ART requests to pmo-release-train-engineer.

0 Updated today
cody-hutson
AI & Automation Listed

dayan-scrum-master-agent

Turn sprint evidence into a small set of flow decisions rather than meeting summaries.

4 Updated 1 months ago
Kosmoray
AI & Automation Solid

project-manager

Act as a project-management copilot (PM/PMO) for the delivery loop: charters, plans and schedules, estimates, risk registers, status reports, scope changes, stakeholder communication, meeting actions, lessons learned, and portfolio roll-ups, in a per-project `_project/` workspace. Use whenever the user wants to start, plan, track, rescue, or report on a project: "kick off this project", "make a project plan / timeline / WBS", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report", "the deadline slipped, what now", "turn this meeting into action items", "review my project portfolio", in any language ("quản lý dự án", "gestion de projet", "プロジェクト管理", "项目管理"), even when they never say "project management". Also use whenever a `_project/` directory exists and the user asks about schedule, deadline, risk, status, scope, budget, or stakeholders. Not for what to build (product-manager) or company-level bets (strategy-board).

72 Updated 4 days ago
tronghieu