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 |
config.example.yaml
View on GitHub# Scrum Master Agent - Notification Configuration Example
#
# Copy this file to 'config.yaml' and customize with your webhook URLs
# Alternatively, use environment variables (see README.md)
notifications:
# Enable/disable notifications (default: false)
enabled: false
# Channel selection: slack or teams
channel: slack
# Slack webhook URL
# Get webhook URL from: https://api.slack.com/messaging/webhooks
# Example: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXX
slack_webhook: https://hooks.slack.com/services/YOUR/WEBHOOK/URL
# Microsoft Teams webhook URL
# Get webhook URL from Teams channel -> Connectors -> Incoming Webhook
# Example: https://outlook.office.com/webhook/xxxx-xxxx-xxxx/IncomingWebhook/yyyy-yyyy-yyyy
teams_webhook: https://outlook.office.com/webhook/YOUR/WEBHOOK/URL
# ================================================================================
# SETUP INSTRUCTIONS
# ================================================================================
# Option 1: YAML Configuration File (Recommended)
# ------------------------------------------------
# 1. Copy this file: cp config.example.yaml config.yaml
# 2. Edit config.yaml with your webhook URLs
# 3. Set enabled: true
# 4. Choose channel: slack or teams
# 5. Save and use skill - notifications will work automatically
# Option 2: Environment Variables
# --------------------------------
# Set these environment variables before running:
#
# export NOTIFY_ENABLED=true
# export NOTIFY_CHANNEL=slack
# 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 Setup:
# ------------
# 1. Go to: https://api.slack.com/messaging/webhooks
# 2. Click "Create your Slack app"
# 3. Choose "From scratch"
# 4. Name your app (e.g., "Scrum Master Bot")
# 5. Select workspace
# 6. Go to "Incoming Webhooks" -> Activate
# 7. Click "Add New Webhook to Workspace"
# 8. Choose channel (e.g., #sprint-updates)
# 9. Copy webhook URL
# 10. Paste into slack_webhook field above
# Microsoft Teams Setup:
# ----------------------
# 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. Click "Configure"
# 6. Name webhook (e.g., "Scrum Master Updates")
# 7. Optionally upload icon
# 8. Click "Create"
# 9. Copy webhook URL
# 10. Paste into teams_webhook field above
# ================================================================================
# NOTIFICATION FORMAT
# ================================================================================
# Notifications are token-efficient (50-100 tokens max) and include:
# - Sprint name and status
# - Velocity (current/committed points)
# - Sprint health score (0-100)
# - Completion percentage
# - Top 3 risks (if any)
#
# Slack format: Rich blocks with emoji indicators
# Teams format: Adaptive Cards with fact sets
# ================================================================================
# USAGE EXAMPLES
# ================================================================================
# Automatic notification (in user request):
# "Generate daily standup summary and send to Slack"
#
# Programmatic notification (in Python):
# formatter.format_standup_summary(metrics, send_notification=True)
#
# Manual notification test:
# from notify_channels import NotificationManager
# manager = NotificationManager('config.yaml')
# manager.send_sprint_summary(metrics)
# ================================================================================
# SECURITY NOTES
# ================================================================================
# - NEVER commit config.yaml with real webhook URLs to version control
# - Add config.yaml to .gitignore
# - Rotate webhook URLs if compromised
# - Use environment variables in CI/CD pipelines
# - Webhook URLs grant write access - keep them secret
# - Consider using separate webhooks for dev/staging/prod
# ================================================================================
# TROUBLESHOOTING
# ================================================================================
# Notifications not working?
# --------------------------
# 1. Check enabled: true in config.yaml
# 2. Verify webhook URL is correct (test in browser - should return error)
# 3. Check channel matches webhook (slack vs teams)
# 4. Verify network connectivity (firewall/proxy)
# 5. Check skill logs for error messages
# 6. Test webhook with curl:
#
# Slack:
# curl -X POST -H 'Content-Type: application/json' \
# -d '{"text":"Test from Scrum Master"}' \
# YOUR_SLACK_WEBHOOK_URL
#
# Teams:
# curl -X POST -H 'Content-Type: application/json' \
# -d '{"text":"Test from Scrum Master"}' \
# YOUR_TEAMS_WEBHOOK_URL
# ================================================================================
# ADVANCED: JSON Configuration
# ================================================================================
# If you prefer JSON over YAML, create config.json:
# {
# "notifications": {
# "enabled": false,
# "channel": "slack",
# "slack_webhook": "https://hooks.slack.com/services/YOUR/WEBHOOK/URL",
# "teams_webhook": "https://outlook.office.com/webhook/YOUR/WEBHOOK/URL"
# }
# }
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: 470k | 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 |