Claude Desktop Integration Examples

This document provides comprehensive real-world examples of using the Gira MCP server with Claude Desktop for project management, team coordination, and development workflow automation.

🚀 Quick Start Example

Basic Project Overview

You: Show me the current state of our project

Claude: I'll get an overview of your project using the Gira MCP tools.

*Uses get_enhanced_board_state with full context*

Here's your current project state:

**Board Overview:**
- **Backlog**: 15 tickets (includes EPIC-001 authentication work)
- **Todo**: 8 tickets ready for development
- **In Progress**: 5 tickets (3 by backend team, 2 by frontend)
- **Review**: 3 tickets awaiting approval
- **Done**: 12 tickets completed this sprint

**Key Metrics:**
- Overall completion: 27.9% (12/43 tickets)
- Active sprint progress: 72% complete
- 3 active epics in progress

Would you like me to dive deeper into any specific area?

📊 Sprint Planning Session

Sprint Planning Conversation

You: Help me plan our next sprint starting February 15th

Claude: I'll help you plan your sprint. Let me first check what tickets are available and create the sprint.

*Uses list_tickets with status="todo" and "backlog"*
*Uses create_sprint with appropriate parameters*

I've created **Sprint Q1-3** starting February 15th with a 14-day duration.

**Available Tickets for Planning:**
From **EPIC-001 (User Authentication)**:
- GCM-123: Login form validation (5 pts, High priority)
- GCM-124: OAuth2 integration (8 pts, High priority)
- GCM-125: Password reset flow (3 pts, Medium priority)

From **EPIC-002 (Dashboard UI)**:
- GCM-201: Dashboard layout (5 pts, Medium priority)
- GCM-202: Data visualization (8 pts, Low priority)

**Recommendations:**
Based on your team's velocity of 25 story points per sprint, I suggest:
1. Add GCM-123, GCM-124, GCM-125 (16 pts total)
2. Add GCM-201 (5 pts) for UI progress
3. Reserve 4 pts for bug fixes and technical debt

Should I add these tickets to the sprint?

You: Yes, add those tickets to the sprint

Claude: *Uses add_tickets_to_sprint with the recommended tickets*

Perfect! I've added 4 tickets (21 story points) to Sprint Q1-3:
- GCM-123: Login form validation → Sprint Q1-3
- GCM-124: OAuth2 integration → Sprint Q1-3  
- GCM-125: Password reset flow → Sprint Q1-3
- GCM-201: Dashboard layout → Sprint Q1-3

The sprint is ready to start. Would you like me to:
1. Start the sprint now
2. Assign tickets to team members
3. Set up sprint goals and milestones

🔄 Daily Standup Automation

Morning Standup Report

You: Give me a standup report for today

Claude: Here's your daily standup report for today:

*Uses get_sprint with current active sprint*
*Uses get_swimlane_tickets grouped by assignee*

## 📅 Daily Standup - February 18, 2024

### **Sprint Q1-3 Progress** (Day 4 of 14)
- **Overall Progress**: 45% complete (9/20 story points)
- **Burndown Status**: Slightly ahead of schedule
- **Days Remaining**: 10 days

### **Team Progress**

**Sarah (@sarah.dev)**
- **Completed Yesterday**: GCM-123 (Login form validation) ✅
- **Today's Focus**: GCM-124 (OAuth2 integration) - 60% complete
- **Blockers**: Waiting for API keys from DevOps

**Mike (@mike.frontend)**  
- **Completed Yesterday**: GCM-201 layout wireframes
- **Today's Focus**: GCM-201 (Dashboard layout) implementation
- **Status**: On track, no blockers

**Alex (@alex.backend)**
- **Completed Yesterday**: Database schema for auth
- **Today's Focus**: GCM-124 backend support
- **Collaboration**: Pairing with Sarah on OAuth integration

### **Sprint Health** 🟢
- **Velocity**: 2.25 points/day (target: 1.43)
- **Scope Changes**: None
- **Risk Level**: Low

### **Action Items**
- [ ] Sarah: Follow up on API keys with DevOps
- [ ] Team: Schedule OAuth integration sync for Wednesday

Need me to update any ticket statuses or create follow-up tasks?

🐛 Incident Response Workflow

Bug Triage and Assignment

You: We have a critical login bug reported by users. Help me handle this

Claude: I'll help you manage this critical issue. Let me create a high-priority ticket and coordinate the response.

*Uses create_ticket with appropriate priority and details*

I've created **GCM-315: Critical login bug** with the following setup:

**Ticket Details:**
- **Priority**: Critical
- **Type**: Bug  
- **Status**: Todo (ready for immediate pickup)
- **Epic**: EPIC-001 (User Authentication)
- **Labels**: critical, security, user-facing

**Immediate Actions Taken:**
1. ✅ Created ticket with critical priority
2. ✅ Added to authentication epic
3. ✅ Tagged with appropriate labels

**Recommended Next Steps:**
1. **Assign to expert**: Should I assign this to Sarah (@sarah.dev) who's working on auth?
2. **Sprint impact**: Add to current sprint or handle separately?
3. **Communication**: Notify team via comment?

You: Assign it to Sarah and add it to the current sprint

Claude: *Uses update_ticket to assign to Sarah*
*Uses add_tickets_to_sprint for current sprint*
*Uses create_comment with notification*

Done! I've set up the critical bug response:

✅ **Assigned** GCM-315 to Sarah (@sarah.dev)
✅ **Added** to Sprint Q1-3 (may impact capacity)
✅ **Notified** team: "Critical login issue reported. Sarah assigned for immediate investigation."

**Sprint Impact Analysis:**
- Previous capacity: 20 story points
- Critical bug effort: ~3 story points (estimated)
- **Recommendation**: Consider moving GCM-202 (low priority) to next sprint

Should I adjust the sprint scope to accommodate this critical fix?

You: Yes, move GCM-202 to the backlog

Claude: *Uses remove_tickets_from_sprint*
*Uses update_ticket to move back to backlog*

Perfect! I've adjusted the sprint:

✅ **Moved** GCM-202 (Data visualization) back to backlog
✅ **Updated** sprint capacity to handle critical bug
✅ **Maintained** sprint focus on core authentication features

**Updated Sprint Scope:**
- Core auth work: 16 points
- Dashboard layout: 5 points  
- Critical bug fix: 3 points
- **Total**: 24 points (within team capacity)

The sprint is rebalanced for the critical issue. Sarah can focus on the bug while maintaining sprint goals.

📈 Progress Reporting

Weekly Status Report

You: Generate a weekly progress report for management

Claude: I'll create a comprehensive weekly progress report. Let me gather all the relevant metrics.

*Uses get_sprint_metrics for current sprint*
*Uses list_epics with progress data*
*Uses get_enhanced_board_state with analytics*

# 📊 Weekly Progress Report
## Week of February 12-18, 2024

### **Executive Summary**
Strong progress across all initiatives with 78% of planned work completed. Authentication epic ahead of schedule, dashboard work progressing well. One critical issue resolved without impacting delivery timeline.

---

### **🏃‍♂️ Sprint Performance**

**Sprint Q1-3** (Feb 15-28, 2024)
- **Duration**: Day 4 of 14
- **Velocity**: 2.1 points/day (↑ 40% vs last sprint)
- **Completion**: 78% of planned scope
- **Health Score**: 🟢 Excellent

**Burndown Analysis:**
- **Planned**: 20 story points total
- **Completed**: 15.6 story points (78%)
- **Remaining**: 4.4 story points
- **Projection**: On track for early completion

---

### **🎯 Epic Progress**

**EPIC-001: User Authentication** (75% complete)
- **Status**: Active, ahead of schedule
- **Completed**: 15/20 story points
- **Key Achievements**: 
  - ✅ Login form validation complete
  - ✅ OAuth2 integration 90% done
  - ✅ Critical login bug resolved in 4 hours
- **Next Week**: Password reset flow, security testing

**EPIC-002: Dashboard UI** (40% complete)
- **Status**: Active, on schedule
- **Completed**: 8/20 story points
- **Key Achievements**:
  - ✅ Dashboard layout framework
  - 🔄 Component library integration (in progress)
- **Next Week**: Data visualization components

---

### **👥 Team Performance**

**Velocity Trends:**
- **Current Sprint**: 2.1 pts/day
- **Last Sprint**: 1.5 pts/day  
- **Team Average**: 1.8 pts/day
- **Trend**: ↗️ Improving (+17% month-over-month)

**Individual Contributions:**
- **Sarah (Backend)**: 7 pts completed, leading OAuth work
- **Mike (Frontend)**: 5 pts completed, dashboard expertise
- **Alex (Full-stack)**: 3.6 pts completed, strong collaboration

---

### **🚨 Issues & Risks**

**Resolved This Week:**
- ✅ **GCM-315**: Critical login bug (resolved in 4 hours)
- ✅ **API Keys**: DevOps coordination improved

**Current Risks:**
- 🟡 **Low**: OAuth testing complexity may need extra day
- 🟢 **Mitigated**: Sprint scope adjusted for critical work

---

### **📅 Next Week Priorities**

1. **Complete Authentication Epic** (Target: 95% done)
   - Finish OAuth2 integration
   - Complete security testing
   - Deploy to staging environment

2. **Advance Dashboard Work** (Target: 60% done)
   - Complete data visualization
   - User testing feedback integration

3. **Planning Activities**
   - Sprint Q1-4 planning session
   - Q2 epic roadmap review

---

### **🎯 Success Metrics**

- **Sprint Completion Rate**: 78% (↑ from 65% last sprint)
- **Bug Resolution Time**: 4 hours average (↓ from 2 days)
- **Team Satisfaction**: High (based on standup feedback)
- **Code Quality**: Stable (0 critical issues in production)

**Forecast**: Current trajectory suggests Sprint Q1-3 will complete 2 days early, allowing for Q1-4 prep time.

Would you like me to dive deeper into any specific area or create additional reports?

🔧 Development Workflow Integration

Feature Development Cycle

You: I want to start working on a new payment integration feature

Claude: I'll help you set up the complete workflow for the payment integration feature. Let me create the epic and initial tickets.

*Uses create_epic for the payment integration*
*Uses create_ticket for multiple related tickets*

I've set up your **Payment Integration** feature workflow:

## 🏗️ **EPIC-003: Payment Integration System**

**Epic Overview:**
- **Goal**: Implement secure payment processing with Stripe
- **Timeline**: 6 weeks (Feb 19 - Apr 1)
- **Owner**: Assigned to you
- **Labels**: payments, security, integration

**Initial Ticket Structure:**

### **Phase 1: Foundation** (Week 1-2)
- **GCM-401**: Payment gateway research and design (5 pts)
- **GCM-402**: Database schema for payment data (3 pts)
- **GCM-403**: API security architecture (8 pts)

### **Phase 2: Core Implementation** (Week 3-4)
- **GCM-404**: Stripe API integration (13 pts)
- **GCM-405**: Payment form UI components (8 pts)
- **GCM-406**: Transaction state management (5 pts)

### **Phase 3: Testing & Polish** (Week 5-6)
- **GCM-407**: Payment flow testing (5 pts)
- **GCM-408**: Error handling and edge cases (3 pts)
- **GCM-409**: Security audit and compliance (8 pts)

**Epic Summary:**
- **Total Scope**: 58 story points
- **Estimated Duration**: 6 weeks
- **Team Capacity**: 10 points/week = 60 points available

**Recommended Next Steps:**
1. Should I add the first phase tickets to the next sprint?
2. Would you like me to set up the epic milestones?
3. Need me to coordinate with other team members?

You: Add the foundation tickets to the next sprint and set up milestones

Claude: *Uses create_sprint for next sprint*
*Uses add_tickets_to_sprint with foundation tickets*
*Uses update_epic with milestone details*

Perfect! I've set up your payment integration workflow:

## ✅ **Sprint Q1-4** (Feb 22 - Mar 7)
Added foundation tickets:
- GCM-401: Payment gateway research → Sprint Q1-4
- GCM-402: Database schema design → Sprint Q1-4  
- GCM-403: API security architecture → Sprint Q1-4

**Sprint Capacity**: 16 points planned (within team limits)

## 🎯 **Epic Milestones**
- **Milestone 1** (Mar 7): Foundation complete, ready for implementation
- **Milestone 2** (Mar 21): Core payment processing functional
- **Milestone 3** (Apr 1): Security audit complete, ready for production

**Development Workflow Ready:**
✅ Epic created with clear scope
✅ Tickets prioritized and estimated  
✅ First sprint populated
✅ Milestones established
✅ Timeline mapped to team capacity

You can now start development! Want me to:
- Assign specific tickets to team members?
- Set up automated progress tracking?
- Create technical specification templates?

🎨 Custom Workflow Examples

Release Planning Session

You: Help me plan our Q2 release based on current epic progress

Claude: I'll analyze your current epic progress and help plan the Q2 release. Let me gather comprehensive data.

*Uses list_epics with status filtering*
*Uses get_epic_tickets for each active epic*
*Uses get_sprint_metrics for velocity analysis*

# 🚀 Q2 Release Planning Analysis

## **Current Epic Status** (as of February 18)

### **Ready for Q2 Release**
**EPIC-001: User Authentication** ✅ 
- **Progress**: 75% complete
- **Timeline**: Will complete by March 1st
- **Release Ready**: Yes, all core features done

**EPIC-002: Dashboard UI** 🟡
- **Progress**: 40% complete  
- **Timeline**: Completion projected March 15th
- **Release Ready**: Core features yes, advanced features for Q3

### **In Development**
**EPIC-003: Payment Integration** 🔄
- **Progress**: Just started (planning phase)
- **Timeline**: April 1st completion
- **Release Ready**: Yes, fits Q2 timeline

### **Planned for Later**
**EPIC-004: Mobile App** ⏳
- **Status**: Draft, not yet started
- **Recommendation**: Move to Q3 for focused effort

---

## **Q2 Release Recommendation**

### **🎯 Core Release Features** 
1. **Complete User Authentication** (March 1st)
   - Login/logout functionality
   - OAuth2 social login
   - Password reset flow
   - Security compliance

2. **Essential Dashboard** (March 15th)
   - User dashboard layout
   - Basic data visualization
   - Core UI components

3. **Payment Processing** (April 1st)
   - Stripe integration
   - Payment form UI
   - Transaction management
   - Security audit complete

### **📊 Release Metrics**
- **Total Story Points**: 98 points
- **Team Capacity**: 120 points (10 weeks × 12 pts/week)
- **Buffer**: 22 points (18% safety margin)
- **Confidence Level**: High 🟢

### **🗓️ Proposed Timeline**

**March Milestones:**
- Week 1: Complete authentication system
- Week 2: Dashboard core features done
- Week 3: Payment integration starts
- Week 4: Integration testing begins

**April Milestones:**
- Week 1: Payment features complete
- Week 2: Full system integration testing  
- Week 3: Security audit and bug fixes
- Week 4: Release preparation and documentation

**May:**
- Week 1: Production deployment
- Week 2: Monitoring and immediate fixes
- Week 3-4: Q3 planning

Would you like me to:
1. Create the specific sprints for this timeline?
2. Set up milestone tracking?
3. Generate detailed work breakdown?

🔍 Advanced Query Examples

Cross-Epic Analysis

You: Show me how our epics are interconnected and identify dependencies

Claude: I'll analyze the relationships between your epics and identify dependencies.

*Uses list_epics to get all epics*
*Uses get_epic_tickets for each epic*
*Uses complex analysis of ticket relationships*

# 🕸️ Epic Interdependency Analysis

## **Epic Relationship Map**

### **EPIC-001: User Authentication** (Foundation)
**Provides services to:**
- EPIC-002: Dashboard UI (user sessions, permissions)
- EPIC-003: Payment Integration (secure user context)
- EPIC-004: Mobile App (authentication APIs)

**Dependencies:** None (foundational system)
**Critical Path:** YES - blocks all other features

### **EPIC-002: Dashboard UI** (Core Features)
**Depends on:**
- EPIC-001: User Authentication (login state, user data)

**Provides services to:**
- EPIC-003: Payment Integration (payment history display)
- EPIC-004: Mobile App (UI component library)

**Dependencies:** Medium priority

### **EPIC-003: Payment Integration** (Revenue Critical)
**Depends on:**
- EPIC-001: User Authentication (secure transactions)
- EPIC-002: Dashboard UI (payment forms, history)

**Provides services to:**
- EPIC-004: Mobile App (payment APIs)

**Dependencies:** High complexity

### **EPIC-004: Mobile App** (Future Growth)
**Depends on:**
- EPIC-001: Authentication APIs
- EPIC-002: UI component patterns
- EPIC-003: Payment APIs

**Provides services to:** None (consumer application)
**Dependencies:** Blocks future mobile features

---

## **🚨 Critical Path Analysis**

### **Sequence Requirements:**
1. **EPIC-001** must complete first (weeks 1-4)
2. **EPIC-002** can start in parallel but needs auth (weeks 2-6)
3. **EPIC-003** needs both auth and UI foundations (weeks 5-10)
4. **EPIC-004** requires all previous epics (weeks 11-16)

### **Risk Assessment:**
- **🔴 High Risk**: EPIC-001 delay blocks everything
- **🟡 Medium Risk**: EPIC-002 UI changes affect payment UX
- **🟢 Low Risk**: EPIC-003 can adapt to auth/UI changes

---

## **📋 Dependency Management Strategy**

### **Immediate Actions:**
1. **Prioritize EPIC-001 completion** (current focus ✅)
2. **Define API contracts** between epics early
3. **Create integration test scenarios** for epic boundaries

### **Risk Mitigation:**
- **EPIC-001 buffer**: Add 1 week buffer for authentication
- **Parallel development**: UI mockups while auth in progress
- **API-first design**: Define payment APIs before implementation

### **Coordination Points:**
- **Week 4**: Authentication → Dashboard handoff
- **Week 6**: Dashboard → Payment integration planning
- **Week 10**: All epics → Mobile app requirements

Want me to:
- Create specific coordination tickets?
- Set up epic milestone dependencies?
- Generate detailed integration test plans?

🤖 Automation Examples

Smart Ticket Management

You: Set up automated ticket organization for our team

Claude: I'll help you create intelligent automation rules for ticket management. Let me analyze your current patterns first.

*Uses various query tools to analyze ticket patterns*

# 🤖 Smart Ticket Automation Setup

Based on your project patterns, I've identified key automation opportunities:

## **📊 Pattern Analysis**

**Current Ticket Distribution:**
- **Bugs**: 23% of tickets, avg priority: High
- **Features**: 45% of tickets, avg story points: 5.2
- **Tasks**: 32% of tickets, mostly infrastructure

**Assignment Patterns:**
- Sarah: 60% backend, 40% full-stack
- Mike: 80% frontend, 20% design
- Alex: 55% backend, 45% DevOps

---

## **🎯 Recommended Automation Rules**

### **Auto-Assignment Rules**

IF ticket.labels contains "frontend" OR "ui" OR "react" THEN assign to mike@team.com

IF ticket.labels contains "backend" OR "api" OR "database"
THEN assign to sarah@team.com

IF ticket.labels contains "devops" OR "deployment" OR "infrastructure" THEN assign to alex@team.com

IF ticket.type == "bug" AND ticket.priority == "critical" THEN assign to sarah@team.com (tech lead)

### **Auto-Labeling Rules**

IF ticket.title contains "login" OR "auth" OR "oauth" THEN add labels: ["authentication", "security"]

IF ticket.title contains "payment" OR "stripe" OR "transaction" THEN add labels: ["payments", "integration", "security"]

IF ticket.type == "bug" AND ticket.priority == "critical" THEN add labels: ["hotfix", "urgent"]

### **Sprint Auto-Management**

IF ticket.labels contains "hotfix" THEN auto-add to current active sprint

IF ticket.epic == "EPIC-001" AND sprint.current.goal contains "auth" THEN suggest adding to current sprint

Would you like me to implement these automation patterns using the MCP tools?

You: Yes, implement the auto-assignment rules first

Claude: I'll implement the auto-assignment automation using intelligent ticket analysis. Here's how it works:

*Note: This demonstrates the logic - actual implementation would use webhooks or scheduled processes*

## ✅ **Smart Assignment System Active**

### **Assignment Logic Implemented:**

**Frontend Specialist (Mike)**
- Triggers: "frontend", "ui", "react", "css", "component"
- Auto-assigns: GCM-205 (Dashboard components) → Mike
- Success: 3 tickets auto-assigned this week

**Backend Specialist (Sarah)**  
- Triggers: "backend", "api", "database", "server", "auth"
- Auto-assigns: GCM-403 (API security) → Sarah
- Success: 5 tickets auto-assigned this week

**DevOps Specialist (Alex)**
- Triggers: "devops", "deployment", "infrastructure", "ci/cd"
- Auto-assigns: GCM-301 (CI pipeline) → Alex
- Success: 2 tickets auto-assigned this week

**Critical Bug Override:**
- All critical bugs → Sarah (tech lead)
- Escalation path active

### **🎯 Results This Week:**
- **Auto-assigned**: 10/15 new tickets (67% success rate)
- **Manual review**: 5 tickets (complex/cross-functional)
- **Time saved**: ~2 hours of planning meetings

### **📈 Optimization Opportunities:**
- Add "mobile" keyword → Alex (React Native experience)
- Create "security" escalation → Sarah + external audit
- Implement workload balancing (prevent overassignment)

The automation is learning from your team patterns. Want me to add the auto-labeling rules next?

---

🔧 Advanced Integration Patterns

Multi-Team Coordination

You: Help coordinate work between our frontend and backend teams

Claude: I'll set up cross-team coordination using the Gira MCP tools. Let me analyze the current team structure and create coordination workflows.

*Uses get_swimlane_tickets grouped by assignee*
*Uses list_tickets with various filters*
*Uses epic analysis for cross-team dependencies*

# 🤝 Cross-Team Coordination Setup

## **Team Structure Analysis**

### **Frontend Team** (Mike, Lisa)
- **Current Load**: 12 active tickets (24 story points)
- **Focus Areas**: UI components, user experience
- **Dependencies**: Waiting on 3 backend APIs

### **Backend Team** (Sarah, Alex)  
- **Current Load**: 8 active tickets (31 story points)
- **Focus Areas**: APIs, database, security
- **Blockers**: 2 tickets waiting on frontend mockups

---

## **🔄 Coordination Workflows**

### **API-First Development Pattern**
I've identified these coordination points:

**GCM-404: Payment API** (Backend → Frontend)
- Backend: API specification due March 1st
- Frontend: Can start mockups immediately
- Integration: March 5th target

**GCM-405: Payment UI** (Frontend → Backend)  
- Frontend: UI mockups due February 25th
- Backend: Form validation logic starts February 26th
- Testing: Joint session March 3rd

### **Dependency Tracking System**

Dependencies Created: - GCM-405 (Payment UI) blocks GCM-404 (Payment API) - GCM-123 (Login form) blocks GCM-201 (Dashboard) - GCM-403 (Security) blocks GCM-407 (Payment testing)

### **📅 Cross-Team Standup Schedule**
**Monday/Wednesday/Friday**: Full team sync
- Progress updates on shared dependencies  
- Blocker identification and resolution
- API contract reviews

**Tuesday/Thursday**: Async updates via ticket comments
- Individual team focus
- Deep work sessions
- Code review cycles

Would you like me to:
1. Set up automated dependency notifications?
2. Create shared milestone tracking?
3. Generate cross-team progress reports?

This comprehensive set of examples demonstrates how Claude Desktop can integrate seamlessly with the Gira MCP server to provide intelligent project management, team coordination, and development workflow automation. The conversational interface makes complex project operations accessible and efficient.