👥 Team Collaboration Guide

Learn how to use CursorRIPER♦Σ effectively in team environments, ensuring consistent workflows, shared understanding, and synchronized development.

🎯 Collaboration Goals

Effective team collaboration with CursorRIPER♦Σ:

• 🤝 Shared workflow understanding
• 📋 Consistent memory management
• 🛡️ Unified protection strategy
• 🔄 Smooth handoffs
• 📊 Clear progress tracking

Without proper collaboration:

• 🚫 Conflicting approaches
• 🚫 Lost context between developers
• 🚫 Inconsistent protection
• 🚫 Duplicated work

🏗️ Team Setup

1. Shared Framework Configuration

Repository Structure:

project-root/
├── .cursor/
│   └── rules/
│       ├── RIPERsigma1.0.5.mdc    # Core framework
│       ├── team-standards.mdc      # Team customizations
│       └── project-specific.mdc    # Project rules
├── memory-bank/                    # Shared memory
│   ├── projectbrief.md
│   ├── systemPatterns.md
│   └── ...
└── .gitignore                      # Exclude personal

Git Configuration:

# .gitignore
# Include shared memory
!/memory-bank/

# Exclude personal context
/memory-bank/personal/
/memory-bank/backups/*/
*.bak

# Exclude local notes
/memory-bank/*-local.md

2. Team Standards Document

Create team-standards.mdc:

# Team CursorRIPER♦Σ Standards

## Mode Usage
- Daily standup: Report current mode
- Mode switches: Document in PR description
- Feature work: Follow standard flow (R→I→P→E→R)

## Memory Management
- Update memory files before pushing
- Review memory changes in PRs
- Weekly memory sync meetings

## Protection Rules
- All API keys: Ψ₁ (PROTECTED)
- Business logic: Ψ₆ (CRITICAL)
- Shared utilities: Ψ₂ (GUARDED)

## Context Handoff
- Document active context in PRs
- Clear personal context before handoff
- Use context templates for common tasks

3. Role Assignments

Mode Champions:

• Research Champion: Ensures thorough investigation
• Plan Champion: Reviews all specifications
• Execute Champion: Monitors code quality
• Review Champion: Validates implementations

Memory Maintainers:

• Requirements Owner: Maintains σ₁
• Architecture Owner: Maintains σ₂
• Progress Tracker: Maintains σ₅

🔄 Collaboration Workflows

1. Feature Development Workflow

Developer A - Research & Planning:

## Feature: User Notifications
### Day 1 - Research Phase
/research
- Investigated notification services
- Documented findings in σ₃
- Updated requirements in σ₁

### Day 2 - Planning Phase  
/plan
- Created notification architecture
- Updated σ₂ with design decisions
- Detailed plan in σ₄

### Handoff Context
!af src/notifications/    # Feature location
!ac NotificationService   # Main implementation
!adoc "Notification Spec" # Requirements
Status: Ready for implementation

Developer B - Implementation:

## Continuing: User Notifications
### Day 3 - Implementation
/execute
- Retrieved context from handoff
- Implemented according to plan
- Protected critical sections:
  - API keys [Ψ₁]
  - Send logic [Ψ₆]
- Updated progress in σ₅: 60%

### Day 4 - Completion
- Finished implementation
- Updated σ₅: 100%
- Ready for review

Developer C - Review:

## Review: User Notifications
### Day 5 - Review Phase
/review
- Verified against requirements [↗️σ₁:R₁₅]
- Checked protection coverage
- Validated test coverage
- Result: Approved with minor notes

2. Pair Programming Workflow

Driver Setup:

/execute
!af src/feature.js        # Current file
!ac implementFeature()    # Current function
!cs feature.js active     # Mark active

Navigator Guidance:

"Check requirement [↗️σ₁:R₈]"
"This needs protection level Ψ₂"
"Update progress in σ₅"

Role Switch:

# Save driver context
!an "Driver context: feature.js, implementFeature()"

# Navigator becomes driver
!cc                      # Clear
!cm                      # Mode context
# Restore from notepad

3. Code Review Workflow

PR Description Template:

## PR: Implement User Notifications

### Mode History
- RESEARCH: 2024-01-15 (2 hours)
- PLAN: 2024-01-15 (1 hour)
- EXECUTE: 2024-01-16 (4 hours)
- REVIEW: 2024-01-16 (30 min)

### Memory Updates
- σ₁: Added requirement R₂₀
- σ₂: New pattern P₁₂ (Observer)
- σ₅: Feature F₈ complete

### Protection Added
- `src/notify/api.js:10-15` [Ψ₁]
- `src/notify/send.js:*` [Ψ₆]

### Context for Review
!af src/notifications/
!ac sendNotification()
!adoc "Notification Requirements"

Review Checklist:

• Mode progression logical?
• Memory files updated?
• Protection appropriate?
• Context documented?
• Cross-references valid?

📋 Team Protocols

1. Daily Standup Protocol

Format:

## Developer: John
- Current Mode: EXECUTE (Ω₄)
- Current Context: Authentication feature
- Progress: 75% of JWT implementation
- Blockers: Need security review for [Ψ₆] sections
- Next: Complete tests, switch to REVIEW

2. Memory Sync Protocol

Weekly Memory Review:

## Memory Sync Meeting - Week 3

### Requirements (σ₁)
- New: R₂₁, R₂₂
- Updated: R₅ (clarified scope)
- Deprecated: R₃ (replaced by R₂₁)

### Architecture (σ₂)
- New Pattern: P₁₃ (Event sourcing)
- Decision: D₈ (Move to microservices)

### Progress (σ₅)
- Completed: F₅, F₆, F₇
- In Progress: F₈ (80%), F₉ (30%)
- Blocked: F₁₀ (awaiting design)

3. Protection Review Protocol

Monthly Protection Audit:

## Protection Audit - January

### Coverage Report
- Total protected sections: 47
- New this month: 12
- Removed: 3
- Modified: 5

### Team Violations
- Total: 2
- Resolved: 2
- Process improvements: Added pre-commit hook

### Protection Gaps
- Payment processing: Needs Ψ₆
- User data handling: Needs Ψ₁
- API endpoints: Need Ψ₂

4. Context Handoff Protocol

Handoff Document:

## Context Handoff: Authentication Feature

### Current State
- Mode: EXECUTE (60% complete)
- Last action: Implemented token generation

### Active Context
Files:
- src/auth/jwt.service.ts 🟢
- src/auth/refresh.service.ts 🟡
- tests/auth.test.ts 🔴 (needs update)

Code:
- generateToken() ✅
- validateToken() ✅
- refreshToken() ⏳ (in progress)

### Next Steps
1. Complete refreshToken()
2. Update tests
3. Add protection markers
4. Switch to REVIEW

### Notes
- Watch for edge case with expired tokens
- Need security review before merge

🛠️ Team Tools

1. Shared Templates

Feature Template:

## Feature: [Name]
- Lead: [Developer]
- Mode: [Current]
- Started: [Date]
- Target: [Date]
- Status: [%]

### Requirements
- [↗️σ₁:Rx]

### Context
!af [files]
!ac [code]

Bug Template:

## Bug: [Description]
- Severity: [HIGH|MEDIUM|LOW]
- Assigned: [Developer]
- Mode: [Current]

### Investigation (RESEARCH)
- Root cause: 
- Affected files:

### Fix Plan (PLAN)
- Approach:
- Files to modify:

### Implementation (EXECUTE)
- Changes made:
- Tests added:

2. Team Commands

Collaboration Commands:

"Show team progress"          # Overview of all features
"List my assigned items"      # Personal tasks
"Check protection coverage"   # Team-wide audit
"Generate handoff document"   # Context transfer

3. Integration Scripts

Pre-commit Hook:

#!/bin/bash
# .git/hooks/pre-commit

# Check for memory updates
if git diff --cached --name-only | grep -q "memory-bank/"; then
    echo "✓ Memory files updated"
else
    echo "⚠️  Warning: No memory updates detected"
fi

# Check for protection markers
if git diff --cached | grep -q "!c[pcgidt]"; then
    echo "✓ Protection markers found"
fi

# Validate cross-references
./scripts/validate-references.sh

CI/CD Integration:

# .github/workflows/riper-check.yml
name: RIPER Framework Check

on: [push, pull_request]

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - name: Check Memory Files
        run: |
          test -f memory-bank/projectbrief.md
          test -f memory-bank/progress.md
          
      - name: Validate Protection
        run: |
          ./scripts/check-protection.sh
          
      - name: Verify Cross-References
        run: |
          ./scripts/validate-xrefs.sh

💡 Team Best Practices

1. Communication

• Document mode switches
• Explain protection decisions
• Share context changes
• Update memory promptly

2. Consistency

• Follow team standards
• Use agreed patterns
• Maintain naming conventions
• Apply protection uniformly

3. Knowledge Sharing

• Regular framework training
• Share workflow tips
• Document lessons learned
• Mentor new team members

4. Conflict Resolution

• Memory conflicts: Latest reasonable update wins
• Protection disputes: Security/compliance decides
• Mode preferences: Follow standard flow
• Context conflicts: Merge both contexts

5. Continuous Improvement

• Weekly retrospectives
• Framework customization
• Tool development
• Process refinement

📊 Team Metrics

Productivity Metrics

## Team RIPER Metrics - January

### Mode Distribution
- Research: 15% ⚠️ (target: 20%)
- Innovate: 10% ✅
- Plan: 20% ✅
- Execute: 45% ✅
- Review: 10% ⚠️ (target: 15%)

### Memory Health
- Update frequency: Daily ✅
- Cross-references: 95% valid ✅
- Protection coverage: 88% ⚠️

### Collaboration
- Handoffs: 12 (smooth: 10, issues: 2)
- PR cycle time: 4.5 hours ✅
- Context clarity: 8/10

Quality Metrics

## Quality Indicators

### Protection Effectiveness
- Violations prevented: 23
- Critical code protected: 100%
- Security issues: 0 ✅

### Memory Accuracy
- Requirements up-to-date: 95%
- Progress accuracy: 90%
- Architecture current: 85%

### Workflow Compliance
- Standard flow followed: 78%
- Mode discipline: 85%
- Context management: 80%

🚨 Common Team Issues

1. Memory Conflicts

Problem: Multiple updates to same file Solution:

• Pull before updating
• Merge thoughtfully
• Communicate changes

2. Context Loss

Problem: Handoff missing information Solution:

• Use handoff template
• Document in PR
• Verbal handoff when complex

3. Protection Inconsistency

Problem: Different protection standards Solution:

• Team protection guide
• Regular audits
• Automated checks

4. Mode Confusion

Problem: Unclear when to switch modes Solution:

• Mode champions
• Clear triggers
• Team training

🎓 Onboarding New Team Members

Day 1: Framework Basics

• Install framework
• Read core concepts
• Practice mode switches
• Understand memory files

Day 2: Team Standards

• Review team customizations
• Learn protection rules
• Practice context management
• Understand workflows

Day 3: Hands-on Practice

• Pair programming session
• Simple feature workflow
• Code review participation
• Memory update practice

Week 1: Integration

• Assigned mentor
• First solo feature
• Team standup participation
• Framework feedback

📚 Related Topics

• Framework Overview
• Mode Transitions
• Memory Management
• BMAD Enterprise

---

← Context Management | Home | Reference →