alirezarezvani/claude-code-skill-factory / generated-skills/scrum-master-agent
scrum-master-agent
VerifiedComprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
| File | Kind | Size |
|---|---|---|
| HOW_TO_USE.md | markdown | 9.3 KB |
| README.md | markdown | 14.3 KB |
| SKILL.md | skill md | 12.9 KB |
| calculate_metrics.py | script | 17.2 KB |
| config.example.yaml | config | 5.4 KB |
| detect_context.py | script | 8.2 KB |
| expected_output.json | config | 2.2 KB |
| format_output.py | script | 16.2 KB |
| notify_channels.py | script | 12.4 KB |
| parse_input.py | script | 9.3 KB |
| prioritize_backlog.py | script | 12.2 KB |
| sample_input_csv.csv | other | 547 B |
| sample_input_jira.json | config | 1.5 KB |
| sample_input_linear.json | config | 2.1 KB |
| tool_adapters.py | script | 12.2 KB |
README.md
View on GitHub# Scrum Master Agent - Installation & Validation
## Overview
A production-ready Scrum Master assistant skill for Claude Code with comprehensive sprint analytics, intelligent context-aware output, and multi-tool integration (Linear, Jira, GitHub Projects, Azure DevOps).
**Key Features**:
- 6 metric calculations: velocity, burndown, capacity, priority scoring, sprint health, retrospective analysis
- Multi-format input parsing: JSON, CSV, YAML
- Context-aware output: Adapts to Claude AI Desktop vs Claude Code CLI
- Token-efficient reporting: 50-1000 tokens depending on report type
- **Notification Integration**: Optional Slack and MS Teams webhook support (disabled by default)
- Tool adapters: Linear, Jira, GitHub Projects, Azure DevOps
**Skill Size**: 30 KB (compressed)
**Python Modules**: 7 files (parse_input, tool_adapters, calculate_metrics, detect_context, format_output, prioritize_backlog, notify_channels)
**Sample Data**: 3 formats (Linear JSON, Jira JSON, CSV)
---
## Installation
### Option 1: Claude Code (Recommended)
```bash
# Copy skill folder to Claude Code skills directory
cp -r scrum-master-agent ~/.claude/skills/
# Verify installation
ls -la ~/.claude/skills/scrum-master-agent
```
### Option 2: Claude AI Desktop
1. Locate the ZIP file: `scrum-master-agent.zip`
2. Open Claude Desktop
3. Drag and drop `scrum-master-agent.zip` into the chat
4. Skill will be imported automatically
### Option 3: Project-Level Installation
```bash
# For project-specific installation
mkdir -p .claude/skills
cp -r scrum-master-agent .claude/skills/
# Verify installation
ls -la .claude/skills/scrum-master-agent
```
---
## Notification Setup (Optional)
Notifications are **completely optional** and **disabled by default**. The skill works perfectly without any notification setup.
### Quick Setup
**Step 1: Get Webhook URL**
*For Slack*:
1. Go to https://api.slack.com/messaging/webhooks
2. Create a Slack app (or use existing)
3. Activate "Incoming Webhooks"
4. Add webhook to workspace and select channel (e.g., #sprint-updates)
5. Copy webhook URL
*For Microsoft Teams*:
1. Open Teams channel where you want notifications
2. Click "..." (More options) next to channel name
3. Select "Connectors"
4. Search for "Incoming Webhook"
5. Configure webhook (name: "Scrum Master Updates")
6. Copy webhook URL
**Step 2: Configure Skill**
*Option A: Configuration File (Recommended)*
```bash
# Copy example config
cp config.example.yaml config.yaml
# Edit config.yaml:
# - Set enabled: true
# - Choose channel: slack or teams
# - Paste your webhook URL
```
*Option B: Environment Variables*
```bash
export NOTIFY_ENABLED=true
export NOTIFY_CHANNEL=slack # or teams
export SLACK_WEBHOOK_URL=https://hooks.slack.com/services/YOUR/WEBHOOK/URL
# OR
export TEAMS_WEBHOOK_URL=https://outlook.office.com/webhook/YOUR/WEBHOOK/URL
```
**Step 3: Use with Skill**
```
@scrum-master-agent
Generate daily standup and send notification to Slack.
```
### Notification Format
Notifications are **token-efficient** (50-100 tokens max) and include:
- Sprint name and status
- Velocity metrics (current/committed points)
- Sprint health score (0-100)
- Completion percentage
- Top 3 risks only (conditional)
**Slack Format**: Rich blocks with emoji indicators
**Teams Format**: Adaptive Cards with fact sets
### Security Notes
- Webhook URLs grant write access - keep them secret
- Never commit config.yaml with real webhook URLs to version control
- Add config.yaml to .gitignore
- Consider using separate webhooks for dev/staging/prod
- Rotate webhook URLs if compromised
### Troubleshooting
**Notifications not working?**
1. Check `enabled: true` in config.yaml
2. Verify webhook URL is correct
3. Ensure channel matches webhook (slack vs teams)
4. Check network connectivity (firewall/proxy)
5. Test webhook with curl:
```bash
# Slack test
curl -X POST -H "Content-Type: application/json" \
-d '{"text":"Test from Scrum Master"}' \
YOUR_SLACK_WEBHOOK_URL
# Teams test
curl -X POST -H "Content-Type: application/json" \
-d '{"text":"Test from Scrum Master"}' \
YOUR_TEAMS_WEBHOOK_URL
```
See [config.example.yaml](config.example.yaml) for complete documentation.
---
## Validation
### Step 1: Check File Structure
```bash
scrum-master-agent/
├── SKILL.md # Main skill definition
├── README.md # This installation guide
├── HOW_TO_USE.md # Usage examples
├── parse_input.py # Multi-format parser (JSON/CSV/YAML)
├── tool_adapters.py # Tool adapters (Linear/Jira/GitHub/Azure)
├── calculate_metrics.py # All 6 metric calculations
├── detect_context.py # Environment detection (Desktop/CLI)
├── format_output.py # Context-aware formatting
├── prioritize_backlog.py # Priority scoring (value/effort/risk)
├── notify_channels.py # Slack & Teams integration
├── config.example.yaml # Configuration template
├── sample_input_linear.json # Linear sample data
├── sample_input_jira.json # Jira sample data
├── sample_input_csv.csv # CSV sample data
└── expected_output.json # Expected results
```
**Total**: 15 files (7 Python modules, 3 documentation files, 4 sample data files, 1 config template)
### Step 2: Validate YAML Frontmatter
```bash
# Check SKILL.md has valid YAML
head -5 scrum-master-agent/SKILL.md
```
**Expected Output**:
```yaml
---
name: scrum-master-agent
description: Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
---
```
**Validation Checklist**:
- ✅ Name is kebab-case (lowercase with hyphens)
- ✅ Description is one line (under 200 chars)
- ✅ YAML opens and closes with `---`
### Step 3: Test with Sample Data
```bash
# Quick test invocation
claude --continue
@scrum-master-agent
Generate a daily standup summary using the attached Linear sample data.
[Attach: sample_input_linear.json]
```
**Expected Output** (50-100 tokens):
```
🚀 Sprint 45 - Day 7/14
✅ Completed: 11 pts
🔄 In Progress: 2 stories
⚠️ Blocked: 1 story
Velocity: Behind schedule
```
### Step 4: Validate Python Modules
```bash
# Check Python syntax (requires Python 3.8+)
cd scrum-master-agent
python3 -m py_compile parse_input.py
python3 -m py_compile tool_adapters.py
python3 -m py_compile calculate_metrics.py
python3 -m py_compile detect_context.py
python3 -m py_compile format_output.py
python3 -m py_compile prioritize_backlog.py
python3 -m py_compile notify_channels.py
```
**No errors?** ✅ Python modules are valid.
---
## Usage Examples
### Quick Examples
**1. Daily Standup (Ultra-Lightweight)**
```
@scrum-master-agent
Quick standup for Sprint 45 [attach: linear_export.json]
```
**Output**: 50-100 tokens
**2. Sprint Planning**
```
@scrum-master-agent
Plan Sprint 46, capacity 80 pts [attach: backlog.csv]
```
**Output**: 200-500 tokens
**3. Sprint Review**
```
@scrum-master-agent
Full sprint review for Sprint 45 [attach: jira_export.json]
```
**Output**: 500-1000 tokens
**4. Retrospective**
```
@scrum-master-agent
Generate retrospective with action items [attach: github_export.json]
```
**Output**: 300-500 tokens
See **HOW_TO_USE.md** for 10+ detailed examples.
---
## Key Capabilities
### 1. Velocity Analysis
- Current vs committed velocity
- Historical average (3-5 sprints)
- Trend analysis (improving/declining/stable)
- Forecast for next sprint
### 2. Burndown Tracking
- Ideal vs actual burndown comparison
- Predictive completion date (linear regression)
- Daily velocity calculation
- On-track alerts
### 3. Capacity Planning
- Team availability calculation (PTO, holidays, meetings)
- Story point allocation with buffer recommendation
- Per-member utilization tracking
- Overallocation warnings
### 4. Priority Scoring
- **Formula**: `(value * 2 + (10 - effort) + (10 - risk)) / 4`
- **Value**: Business impact (High=10, Medium=5, Low=2)
- **Effort**: Story points (normalized, inverse)
- **Risk**: Blockers, dependencies, complexity
- **Output**: P0/P1/P2/P3 recommendations
### 5. Sprint Health Score (0-100)
- **Velocity**: 40% weight
- **Burndown**: 30% weight
- **Blocked Items**: 20% weight
- **Team Morale**: 10% weight (optional)
- **Rating**: Excellent (90+), Good (70-89), Fair (50-69), At Risk (<50)
### 6. Retrospective Analysis
- Completed vs committed stories
- Blocked item analysis (count, duration, causes)
- Cycle time metrics (avg time from start to done)
- Action item generation (P0/P1/P2)
---
## Multi-Tool Integration
### Supported Tools
| Tool | Format | Adapter | Sample File |
|------|--------|---------|-------------|
| **Linear** | JSON | `LinearAdapter` | `sample_input_linear.json` |
| **Jira** | JSON/CSV | `JiraAdapter` | `sample_input_jira.json` |
| **GitHub Projects** | CSV/JSON | `GitHubAdapter` | Use CSV export |
| **Azure DevOps** | JSON/CSV | `AzureDevOpsAdapter` | Use work item query |
### Exporting Data
**Linear**:
1. Open project view
2. Click "..." → Export → JSON
3. Use exported file with skill
**Jira**:
1. Use REST API: `GET /rest/api/3/search?jql=sprint={sprint_id}`
2. Or export to CSV from sprint board
**GitHub Projects**:
1. Open project board
2. Export to CSV (3-dot menu)
3. Use CSV with skill
**Azure DevOps**:
1. Create work item query
2. Export results to JSON/CSV
3. Use exported file with skill
---
## Context-Aware Output
### Claude AI Desktop
- ✅ Rich markdown tables
- ✅ Emoji indicators (🚀, ✅, ⚠️)
- ✅ Detailed reports (high token budget)
- ❌ No ANSI colors
- ❌ No ASCII charts
### Claude Code (CLI)
- ✅ Markdown tables (terminal-friendly)
- ✅ ASCII charts for trends
- ✅ ANSI color codes for priorities
- ✅ Concise output (medium token budget)
- ❌ No emojis (rendering issues)
### API
- ✅ JSON export format
- ✅ Tool integration support
- ✅ Structured data output
- ❌ No visual elements
**Detection is automatic** - skill adapts based on environment variables and TTY detection.
---
## Token Efficiency
### Summary-First Approach
1. **Summary**: Key metrics in 5-10 lines
2. **Offer Details**: "Want full report?"
3. **Progressive Disclosure**: Drill down on request
### Conditional Alerts
- ✅ Only show warnings/risks if they exist
- ✅ Don't report "No issues" (wastes tokens)
- ✅ Prioritize top 3-5 recommendations
### Lazy Calculation
- ✅ Compute only what's requested
- ✅ Cache intermediate results
- ✅ Reuse calculations across reports
### Token Budgets by Report Type
- **Standup**: 50-100 tokens
- **Planning**: 200-500 tokens
- **Review**: 500-1000 tokens
- **Retrospective**: 300-500 tokens
---
## Best Practices
### Data Quality
1. **Consistent Story Pointing**: Use Fibonacci (1,2,3,5,8,13) or T-shirt sizes
2. **Daily Status Updates**: Update story status daily for accurate burndown
3. **Blocked Item Tracking**: Document why items are blocked and who can unblock
4. **Sprint Boundaries**: Don't change scope after day 3 (except critical bugs)
### Workflow Integration
1. **Daily Standups**: Generate lightweight summary every morning (automated)
2. **Sprint Planning**: Use priority scoring to allocate top 80% of capacity
3. **Mid-Sprint Check**: Run health score on day 5-7 to catch issues early
4. **Retrospectives**: Generate within 24 hours of sprint end while feedback is fresh
### Customization
- Adjust priority scoring weights (default: value 50%, effort 30%, risk 20%)
- Configure health score weights (default: velocity 40%, burndown 30%, blocked 20%, morale 10%)
- Set custom buffer percentage (default: 15%)
---
## Troubleshooting
### Common Issues
**"Skill not loaded"**
```bash
# Check skill is in correct location
ls ~/.claude/skills/scrum-master-agent/SKILL.md
# Check YAML frontmatter is valid
head -5 ~/.claude/skills/scrum-master-agent/SKILL.md
```
**"Missing required fields"**
Ensure your data includes: `sprint_name`, `start_date`, `end_date`, `stories` (with `id`, `title`, `points`, `status`)
**"Can't calculate burndown"**
Provide valid `start_date` and `end_date` in ISO 8601 format (YYYY-MM-DD)
**"No historical data"**
Velocity trends require 3+ previous sprints. Provide historical data for better forecasting.
**"Python module not found"**
Ensure all 6 Python files are in the skill folder. Use `ls` to verify.
---
## Dependencies
### Python Version
- **Required**: Python 3.8+
- **Standard Library Only**: No external dependencies
### Python Modules Used
- `json` (JSON parsing)
- `csv` (CSV parsing)
- `yaml` (YAML parsing - if available, falls back to JSON)
- `typing` (Type hints)
- `datetime` (Date calculations)
- `statistics` (Mean, stdev)
- `os`, `sys` (Environment detection)
**No `pip install` required** - uses only Python standard library.
---
## Performance
### Skill Loading
- **Size**: 30 KB compressed
- **Load Time**: <100ms
- **Memory**: <5 MB
### Calculation Performance
- **Parse Input**: <50ms
- **Calculate Metrics**: <200ms
- **Format Output**: <100ms
- **Total**: <350ms per request
**Optimizations**:
- Lazy calculation (compute only what's needed)
- Efficient data structures (lists/dicts)
- Minimal external calls
---
## Version History
**v1.1.0** (2025-11-05)
- Added Slack and MS Teams notification integration
- Optional webhook configuration (disabled by default)
- Token-efficient notifications (50-100 tokens)
- Rich formatting (Slack blocks, Teams Adaptive Cards)
**v1.0.0** (2025-11-05)
- Initial release
- 6 metric calculations (velocity, burndown, capacity, priority, health, retrospective)
- Multi-tool integration (Linear, Jira, GitHub, Azure DevOps)
- Context-aware output formatting (Desktop vs CLI)
- Token-efficient reporting (50-1000 tokens)
- 10+ example use cases
---
## Support
### Documentation
- **SKILL.md**: Complete capability reference
- **HOW_TO_USE.md**: 10+ detailed examples
- **README.md**: This installation guide
### Getting Help
Ask Claude:
- "What metrics can you calculate?"
- "Show me an example of priority scoring"
- "How do I export data from Linear/Jira/GitHub?"
- "What's the best format for my data?"
### Contributing
For issues, feature requests, or contributions, see the Skills Factory repository.
---
## License
MIT License - Free to use, modify, and distribute.
---
**Generated by**: Claude Code Skills Factory
**Date**: 2025-11-05
**Version**: 1.1.0
**Status**: Production-ready ✅
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |