MSP Examples

MSP Implementation Examples

These examples showcase different implementation patterns.

Simple Implementation Examples

1. Basic Session Tracking

# Minimal MSP usage - just start/end
.\msp.ps1 start
# ... do work ...
.\msp.ps1 end --summary "Fixed bug #123"

# Even this simple usage provides:
# - Session duration tracking
# - Work pattern analysis
# - Basic context preservation

2. Decision Documentation Pattern

# Before making any architectural choice
.\msp.ps1 decide @"
Choosing PostgreSQL over MongoDB because:
1. Need ACID transactions for payment processing
2. Relational data model fits our domain
3. Team has more PostgreSQL experience
Alternatives considered: MongoDB, DynamoDB
"@

# Months later, anyone can query:
.\msp.ps1 search "database decision"
> Found: PostgreSQL decision on 2024-08-15
> Rationale: ACID, relational model, team experience

3. Progress Tracking

# Start of sprint
.\msp.ps1 milestone "Sprint 23 Start" --target 85

# Daily updates
.\msp.ps1 update "Completed user story US-456" 72
.\msp.ps1 update "Fixed critical bug" 75
.\msp.ps1 update "Deployed to staging" 78

# Visual progress
.\msp.ps1 progress --visual
> Sprint 23 Progress: ████████░░ 78% (Target: 85%)
> Velocity: +15% this week
> Estimated completion: 2.5 days

4. Blocker Management

# When stuck
.\msp.ps1 blocker "Can't reproduce customer bug locally"

# After investigation
.\msp.ps1 update "Found issue: timezone mismatch in test data"
.\msp.ps1 resolve "Fixed by using UTC in test environment"

# Analytics
.\msp.ps1 blockers --stats
> Average resolution time: 4.2 hours
> Most common: Environment issues (31%)
> Longest blocker: OAuth integration (3 days)

Integration Patterns

Git Commit Integration

# .gitmessage template
[MSP-${SESSION_ID}] ${SUMMARY}

Progress: ${START_PROGRESS}% → ${END_PROGRESS}%
Duration: ${DURATION}

Decisions:
${DECISIONS}

Co-authored-by: MSP <msp@sessionprotocol.dev>

CI/CD Pipeline Integration

# GitHub Actions
- name: MSP Session Start
  run: msp start --ci --job "${{ github.job }}"
  
- name: Run Tests
  run: |
    msp update "Running test suite" 30
    npm test
    
- name: MSP Session End
  if: always()
  run: |
    msp end --status "${{ job.status }}"
    msp export --format json > session-report.json
    
- name: Upload MSP Report
  uses: actions/upload-artifact@v2
  with:
    name: msp-session-${{ github.run_id }}
    path: session-report.json

Getting Started with These Patterns

For 'Low-Code' Vibe Coders

Start with MSP Lite
Focus on start, update, and end commands
Add decision tracking once comfortable
Export context for AI assistance

For Experienced Developers

Implement the NOL Framework, substitute tools as you like
Integrate with your project management tool and other tools you already use

Try It Yourself

Ready to transform your workflow? Start with our 5-minute quickstart or explore the full protocol specification.

Have an interesting MSP use case? Share it with the community in our GitHub Discussions.

Menu