Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
npxskills add alirezarezvani/claude-code-skill-factory--skill scrum-master-agentLoading…
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.
JSON (Recommended):
{
"tool": "linear|jira|github|azure",
"sprint_name": "Sprint 45",
"start_date": "2025-11-05",
"end_date": "2025-11-19",
"team_capacity": 80,
"stories": [...]
}
CSV:
story_id,title,points,status,assignee,priority,blocked
STORY-123,User login,5,In Progress,Alice,High,false
YAML:
sprint:
name: "Sprint 45"
team:
- name: Alice
capacity: 40
- name: Bob
capacity: 40
Tool-Specific Exports:
Token Budget: 50-100 tokens
🚀 Sprint 45 - Day 7/10
✅ Completed: 3 stories (13 pts)
🔄 In Progress: 5 stories (21 pts)
⚠️ Blocked: 1 story (5 pts) - Needs DB access
Velocity: On track (65% complete, 70% time elapsed)
Token Budget: 200-500 tokens
📊 Sprint 45 Planning Summary
Capacity: 80 pts | Committed: 75 pts | Buffer: 5 pts
High Priority (35 pts):
- STORY-123: User authentication (8 pts)
- STORY-124: Payment integration (13 pts)
- STORY-125: Dashboard redesign (8 pts)
Recommendations:
1. P0: Address DB access blocker
2. P1: Reduce scope if velocity drops below 85%
3. P2: Consider splitting STORY-124 (13 pts is risky)
Token Budget: 500-1000 tokens
Includes:
Token Budget: 300-500 tokens
🔍 Sprint 45 Retrospective
What Went Well:
- 95% velocity achievement
- Zero production incidents
- Early story completion (3 days before deadline)
What Needs Improvement:
- 2 stories blocked for >2 days
- Code review delays (avg 18 hours)
Action Items:
[P0] Establish DB access protocol (Owner: Alice, Due: 11/12)
[P1] Set 8-hour code review SLA (Owner: Bob, Due: 11/15)
[P2] Add automated status updates (Owner: Team, Due: 11/20)
For tool integration and dashboards:
{
"sprint": "Sprint 45",
"metrics": {
"velocity": 75,
"completion_rate": 0.95,
"cycle_time_avg": 3.2
},
"risks": [...],
"recommendations": [...]
}
Daily Standup:
@scrum-master-agent
Generate a quick standup summary for Sprint 45 using the attached Linear export.
Sprint Planning:
@scrum-master-agent
Help me plan Sprint 46. Team capacity is 80 points. Here's the backlog (CSV attached).
Prioritize based on effort, value, and risk.
Burndown Analysis:
@scrum-master-agent
Analyze Sprint 45 burndown. Are we on track? When will we likely finish?
Attached: Jira sprint export (JSON)
Retrospective:
@scrum-master-agent
Generate retrospective report for Sprint 45. Focus on blockers and cycle time.
Attached: GitHub Projects export (CSV)
Capacity Planning:
@scrum-master-agent
Calculate team capacity for next sprint. Alice is on PTO for 3 days, Bob has 2 days of meetings.
Team size: 4 engineers (40 pts each normally).
Multi-Tool Comparison:
Compare velocity trends across last 3 sprints using Linear data for Sprint 43-44 and Jira data for Sprint 45.
Risk Analysis:
Identify high-risk stories in the backlog. Flag anything with >8 points, blockers, or missing dependencies.
Custom Metrics:
Calculate sprint health score based on: velocity (40%), burndown trend (30%), blocked items (20%), team morale (10%).
parse_input.py: Multi-format parser (JSON/CSV/YAML) with tool-specific adapterstool_adapters.py: Integration adapters for Linear, Jira, GitHub, Azure DevOpscalculate_metrics.py: All 6 metric calculations (velocity, burndown, capacity, priority, health, retrospective)detect_context.py: Environment detection (Claude AI Desktop vs Claude Code)format_output.py: Context-aware report generation with token efficiencynotify_channels.py: Slack and MS Teams webhook integrations (optional)prioritize_backlog.py: Priority scoring with effort/value/risk analysis1. Velocity Analysis:
2. Burndown Tracking:
3. Capacity Planning:
4. Priority Scoring:
priority_score = (value * 2 + (10 - effort) + (10 - risk)) / 45. Sprint Health Score:
6. Retrospective Analysis:
tool_adapters.pycp -r scrum-master-agent ~/.claude/skills/
Drag the scrum-master-agent.zip file into Claude Desktop.
Use the /v1/skills endpoint to upload the skill package.
Notifications are disabled by default and completely optional. The skill works perfectly without any notification setup.
Option 1: Configuration File (Recommended)
# Copy example config
cp config.example.yaml config.yaml
# Edit config.yaml with your webhook URLs
# Set enabled: true
# Choose channel: slack or teams
Option 2: Environment Variables
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
Getting Webhook URLs:
Slack:
Microsoft Teams:
Using Notifications:
@scrum-master-agent
Generate daily standup summary and send notification to Slack.
Notifications are token-efficient (50-100 tokens max) with:
Version: 1.1.0 (with Notification Support) Last Updated: 2025-11-05 Author: Claude Code Skills Factory License: MIT
For issues, feature requests, or contributions, see the skill's GitHub repository or contact the Skills Factory maintainers.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.