/milestone-tracker

Milestone Tracker

Track and monitor project milestone progress

Instructions

1. **Check Available Tools**

• Verify Linear MCP server connection
• Check GitHub CLI availability
• Test git repository access
• Ensure required permissions

2. **Gather Milestone Data**

• Query Linear for project milestones and roadmap items
• Fetch GitHub milestones and their associated issues
• Analyze git tags for historical release patterns
• Review project documentation for roadmap information
• Collect all active and upcoming milestones

3. **Analyze Milestone Progress** For each milestone:

• Count completed vs. total tasks
• Calculate percentage complete
• Measure velocity trends
• Identify blocking issues
• Track time remaining

4. **Perform Predictive Analysis**

• Calculate burn-down rate from historical data
• Project completion dates based on velocity
• Factor in team capacity and holidays
• Identify critical path items
• Assess confidence levels for predictions

5. **Risk Assessment** Evaluate each milestone for:

• Schedule risk (falling behind)
• Scope risk (expanding requirements)
• Resource risk (team availability)
• Dependency risk (blocked by others)
• Technical risk (unknowns)

6. **Generate Milestone Report** Create comprehensive report showing:

• Milestone timeline visualization
• Progress indicators for each milestone
• Predicted completion dates with confidence
• Risk heat map
• Recommended actions for at-risk items

7. **Track Dependencies**

• Map inter-milestone dependencies
• Identify cross-team dependencies
• Highlight critical path
• Show dependency impact on schedule

8. **Provide Recommendations** Based on analysis:

• Suggest scope adjustments
• Recommend resource reallocation
• Propose timeline changes
• Identify quick wins
• Highlight blockers needing attention

Prerequisites

• Git repository access
• Linear MCP server connection (preferred)
• GitHub milestones or project boards
• Historical velocity data

Command Flow

1. Milestone Discovery

1. Check Linear for project milestones/roadmap items
2. Scan GitHub for milestone definitions
3. Analyze git tags for release history
4. Review README/docs for project roadmap
5. Ask user for additional context if needed

2. Comprehensive Milestone Analysis

Data Collection Sources

Linear/Project Management:
- Milestone definitions and due dates
- Associated tasks and dependencies
- Team assignments and capacity
- Progress percentages
- Blocker status

GitHub:
- Milestone issue tracking
- PR associations
- Release tags and dates
- Branch protection rules

Git History:
- Commit velocity trends
- Feature branch lifecycle
- Release cadence patterns
- Contributor availability

3. Milestone Status Report

# Milestone Tracking Report - [Project Name]
Generated: [Date]

## Executive Summary
- Total Milestones: [Count]
- On Track: [Count] ([%])
- At Risk: [Count] ([%])
- Blocked: [Count] ([%])
- Completed: [Count] ([%])

## Milestone Dashboard

### 🎯 Current Sprint Milestone: [Name]
**Target Date**: [Date] (in [X] days)
**Confidence Level**: [High/Medium/Low]

Progress: ████████░░ 80% Complete

**Key Deliverables**:
- ✅ User Authentication System
- ✅ Database Schema Migration  
- 🔄 API Integration (75%)
- ⏳ Documentation Update (0%)
- ❌ Performance Testing (Blocked)

**Health Indicators**:
- Velocity Trend: ↓ Declining (-15%)
- Burn Rate: 🔴 Behind Schedule
- Risk Level: Medium
- Team Capacity: 85% allocated

### 📅 Upcoming Milestones

#### Q1 2024: Beta Release
**Target**: March 15, 2024
**Status**: 🟡 At Risk

Timeline:

Jan ████████████░░░░░░░░ 60% Feb ░░░░░░░░░░░░░░░░░░░░ 0% Mar ░░░░░░░░░░░░░░░░░░░░ 0%

**Dependencies**:
- Alpha Testing Complete ✅
- Security Audit (In Progress)
- Marketing Website (Not Started)

**Predicted Completion**: March 22 (+7 days)
**Confidence**: 65%

#### Q2 2024: Public Launch
**Target**: June 1, 2024
**Status**: 🟢 On Track

Key Milestones Path:
1. Beta Release → 2. User Feedback Integration → 3. Production Deployment

**Critical Path Items**:
- Infrastructure Setup (Start: April 1)
- Load Testing (Duration: 2 weeks)
- Security Certification (Lead time: 4 weeks)

4. Predictive Analytics

## Completion Predictions

### Machine Learning Model Predictions
Based on historical data and current velocity:

**Beta Release Probability**:
- On Time (Mar 15): 35%
- 1 Week Delay: 45%
- 2+ Week Delay: 20%

**Factors Influencing Prediction**:
1. Current velocity 15% below plan
2. 2 critical dependencies unresolved
3. Team member on leave next week
4. Historical milestone success rate: 72%

### Monte Carlo Simulation Results
Running 1000 simulations based on task estimates:

Completion Date Distribution: Mar 10-15: ████ 20% Mar 16-22: ████████ 40% Mar 23-31: ██████ 30% April+ : ██ 10%

P50 Date: March 19 P90 Date: March 28

### Risk-Adjusted Timeline
Recommended buffer: +5 days
Confident delivery date: March 20

5. Dependency Tracking

## Milestone Dependencies

### Critical Path Analysis
```mermaid
gantt
    title Critical Path to Beta Release
    dateFormat  YYYY-MM-DD
    section Backend
    API Development    :done,    api, 2024-01-01, 30d
    Database Migration :active,  db,  2024-02-01, 14d
    Security Audit     :         sec, after db, 21d
    section Frontend  
    UI Components      :done,    ui,  2024-01-15, 21d
    Integration        :active,  int, after ui, 14d
    User Testing       :         ut,  after int, 7d
    section Deploy
    Infrastructure     :         inf, 2024-03-01, 7d
    Beta Deployment    :crit,    dep, after sec ut inf, 3d

Dependency Risk Matrix

| Dependency | Impact | Likelihood | Mitigation | |------------|--------|------------|------------| | Security Audit Delay | High | Medium | Start process early | | API Rate Limits | Medium | Low | Implement cac