Agent skill · AI & Agents

scrum-master-agent

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codeships scriptsMIT
Install
npx skills add alirezarezvani/claude-code-skill-factory --skill scrum-master-agent --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 15
SKILL.md size: 13 KB
Bundled scripts: yes
Path: generated-skills/scrum-master-agent/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 839
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Scrum Master Agent A production-ready Scrum Master assistant designed for SaaS startups and application engineering teams. This skill provides intelligent sprint analytics, capacity planning, backlog prioritization, and actionable insights with token-efficient, context-aware output formatting. ## Capabilities ### Sprint Management - **Sprint Planning**: Capacity-based story allocation with velocity tracking - **Backlog Grooming**: Priority scoring with effort/value/risk analysis - **Sprint Health Monitoring**: Real-time burndown tracking with predictive alerts - **Velocity Analysis**: Historical trend analysis with forecasting ### Team Operations - **Daily Standups**: Ultra-lightweight progress summaries (50-100 tokens) - **Capacity Planning**: Team availability calculation with holiday/PTO handling - **Sprint Retrospectives**: Action items extraction with sentiment analysis - **Risk Detection**: Automated alerts for scope creep, velocity drops, blocked tasks ### Multi-Tool Integration - **Linear**: Native JSON import with Linear-specific field mapping - **Jira**: REST API adapter with custom field support - **GitHub Projects**: GraphQL integration with issue/PR tracking - **Azur

What's inside
Steps it walks through
  1. Capabilities
  2. Sprint Management
  3. Team Operations
  4. Multi-Tool Integration
  5. Notification Integration
  6. Intelligent Output Design
  7. Input Requirements
  8. Supported Formats
  9. Required Fields
  10. Data Quality
  11. Output Formats
  12. 1. Daily Standups (Ultra-Lightweight)
  13. 2. Sprint Planning (Moderate Detail)
  14. 3. Sprint Review (Full Report)
Ships with 14 files
  • HOW_TO_USE.md
  • README.md
  • calculate_metrics.py
  • config.example.yaml
  • detect_context.py
  • expected_output.json
  • format_output.py
  • notify_channels.py
  • parse_input.py
  • prioritize_backlog.py
  • sample_input_csv.csv
  • sample_input_jira.json
  • sample_input_linear.json
  • tool_adapters.py
Commands it runs
cp -r scrum-master-agent ~/.claude/skills/
Copy example config
cp config.example.yaml config.yaml
Edit config.yaml with your webhook URLs
Set enabled: true
Choose channel: slack or teams
export NOTIFY_ENABLED=true
export NOTIFY_CHANNEL=slack  # or teams
export SLACK_WEBHOOK_URL=https://hooks.slack.com/services/YOUR/WEBHOOK/URL
export TEAMS_WEBHOOK_URL=https://outlook.office.com/webhook/YOUR/WEBHOOK/URL
More from claude-code-skill-factory
All skills →
About this skill
What does the scrum-master-agent skill do?

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

How do I install it?

Run `npx skills add alirezarezvani/claude-code-skill-factory --skill scrum-master-agent --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-code-skill-factory, a repository with 839 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going