scrum-master-agent

# 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
- **Azure DevOps**: Work item queries with sprint hierarchy


### Notification Integration
- **Slack Notifications**: Token-efficient webhook integration with rich block formatting
- **MS Teams Notifications**: Adaptive Card integration for Microsoft Teams channels
- **Optional/Disabled by Default**: No setup required to use skill, notifications opt-in
- **User Choice**: Select Slack or Teams via configuration or environment variables
- **Concise Summaries**: 50-100 token notifications with top 3 risks only
### Intelligent Output Design
- **Context Detection**: Automatically adapts to Claude AI Desktop vs Claude Code
- **Token Efficiency**: Summary-first approach with progressive disclosure
- **Conditional Alerts**: Only shows warnings/risks when they exist
- **Format Optimization**: Markdown tables for Claude AI, ASCII charts for CLI

## Input Requirements

### Supported Formats
1. **JSON** (Recommended):
   ```json
   {
     "tool": "linear|jira|github|azure",
     "sprint_name": "Sprint 45",
     "start_date": "2025-11-05",
     "end_date": "2025-11-19",
     "team_capacity": 80,
     "stories": [...]
   }
   ```

2. **CSV**:
   ```csv
   story_id,title,points,status,assignee,priority,blocked
   STORY-123,User login,5,In Progress,Alice,High,false
   ```

3. **YAML**:
   ```yaml
   sprint:
     name: "Sprint 45"
     team:
       - name: Alice
         capacity: 40
       - name: Bob
         capacity: 40
   ```

4. **Tool-Specific Exports**:
   - Linear: Export to JSON from project view
   - Jira: Use REST API or CSV export
   - GitHub Projects: GraphQL query or CSV export
   - Azure DevOps: Work Item Query Results

### Required Fields
- **Sprint metadata**: name, start_date, end_date, team_capacity
- **Stories**: id, title, points, status, assignee
- **Optional**: priority, blocked, dependencies, labels, created_date

### Data Quality
- Story points must be numeric (Fibonacci or T-shirt sizes)
- Dates in ISO 8601 format (YYYY-MM-DD)
- Status values normalized to: Todo, In Progress, In Review, Done
- Team capacity in story points per sprint

## Output Formats

### 1. Daily Standups (Ultra-Lightweight)
**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)
```

### 2. Sprint Planning (Moderate Detail)
**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)
```

### 3. Sprint Review (Full Report)
**Token Budget**: 500-1000 tokens

Includes:
- Velocity trends (ASCII chart for CLI, table for Claude AI)
- Burndown analysis with predictive completion date
- Team performance metrics (throughput, cycle time)
- Risk alerts (conditional - only if issues exist)
- Prioritized recommendations (P0/P1/P2)

### 4. Retrospective Analysis
**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)
```

### 5. Optional JSON Export
For tool integration and dashboards:
```json
{
  "sprint": "Sprint 45",
  "metrics": {
    "velocity": 75,
    "completion_rate": 0.95,
    "cycle_time_avg": 3.2
  },
  "risks": [...],
  "recommendations": [...]
}
```

## How to Use

### Quick Invocations

**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 en