/complete-sprint

name: complete-sprint
description: Generate comprehensive sprint retrospective from completed epics
argument-hint: <sprint-number-or-folder-path>

Sprint Retrospective Generator

**Sprint:** $ARGUMENTS

---

Workflow Chain

This command generates a comprehensive retrospective after all sprint epics are complete:

/create-epic-plan <epic-key>     → Creates Overview Document
         ↓
/create-implementation-plan <overview-doc-url>  → Creates Implementation Plan
         ↓
/execute-ticket <ticket-key>     → Executes individual tickets
         ↓
/complete-epic <epic-key>        → Completes epic
         ↓
/complete-sprint <sprint-folder> → Sprint retrospective (YOU ARE HERE)

---

Phase 0: Context Retrieval

1. **Determine sprint identifier:**

• If `$ARGUMENTS` is a number (e.g., "1", "2"): Sprint [N]
• If `$ARGUMENTS` is a path: Use as Confluence folder path
• Default folder: `/Epics/Complete/Sprint [N]/`

2. **Locate all epic documents:**

• Scan folder: `/Epics/Complete/Sprint [N]/`
• Find all Overview Documents
• Find all Implementation Plans
• Find all Completion Reports

3. **FAILURE CONDITION - No Documents Found:**

If no epic documents found in the sprint folder:

**STOP and prompt the user:**

   I was unable to locate any completed epics in Sprint $ARGUMENTS.

   Searched location: [folder path]

   Please provide:
   1. Sprint number or folder path: [correct value]
   2. Confluence folder containing completed epics: [paste link]

**DO NOT PROCEED** until confirmed.

4. **MANDATORY CHECKPOINT - Sprint Document Confirmation:**

   Please confirm the following before generating retrospective:

   Sprint: $ARGUMENTS
   Folder: [Confluence folder path]

   Epics Found:
   - {Epic_Key_1}: {Epic_Title_1} ([X] tickets, [Y] points)
   - {Epic_Key_2}: {Epic_Title_2} ([X] tickets, [Y] points)
   - ...

   Total: [count] epics, [total tickets] tickets, [total points] story points

   Is this the correct sprint to analyze? (Yes / No / Correct)

**DO NOT PROCEED** without explicit user confirmation.

---

Phase 1: Document Collection & Analysis

1. **Read all documents in parallel:**

• Load all Overview Documents
• Load all Implementation Plans
• Load all Completion Reports
• Load all related Jira tickets

2. **Extract key data points:**

• Sprint goals (from epic summaries)
• Story points: planned vs. completed
• Ticket counts and statuses
• Cycle times and completion dates
• Test coverage metrics
• Bug counts and patterns
• Technical debt items
• Follow-up tickets created
• Team members involved

3. **Cross-reference data:**

• Verify consistency across documents
• Identify gaps or discrepancies
• Flag incomplete or missing information

---

Phase 2: Parallel Review Tracks

Execute these review tracks **simultaneously** (parallel analysis):

Track 1 - Engineering Excellence

**Focus:** Code quality patterns and technical execution

**Analyze:**

• **Code Quality Patterns:** Common patterns used across epics
• **Anti-Patterns Observed:** Problems that appeared multiple times
• **Technical Debt:**
• Debt introduced: [count items] from [epics]
• Debt resolved: [count items]
• Net change: [+/-]
• **Architecture Decisions:**
• Key decisions made: [list with rationale]
• Impact across codebase: [description]
• **Performance:**
• Bottlenecks identified: [list]
• Optimizations made: [list]
• **Dependency Management:**
• New dependencies added: [count and justification]
• Dependency conflicts: [count and resolution]
• **Build/Deployment:**
• CI/CD pipeline changes: [description]
• Build time trends: [analysis]

Track 2 - Quality Assurance

**Focus:** Testing effectiveness and quality metrics

**Analyze:**

• **Test Coverage:**
• Start of sprint: [%]
• End of sprint: [%]
• Coverage by epic: [breakdown]
• Target met: [Yes/No - 90% target]
• **Testing Gaps:** Areas with insufficient coverage
• **Bug Patterns:**
• Total bugs found: [count]
• Bugs by severity: [critical/high/medium/low]
• Root causes: [common patterns]
• Bugs escaped to production: [count]
• **Regression Issues:**
• Regressions introduced: [count]
• Tests added to prevent: [count]
• **Test Automation:**
• New automated tests: [count]
• Test execution time: [trend analysis]
• Flaky tests: [count and fixes]
• **Edge Cases:**
• Critical edge cases discovered: [list]
• Edge cases not caught by initial planning: [list]

Track 3 - Security & Compliance

**Focus:** Security posture and compliance adherence

**Analyze:**

• **Security Vulnerabilities:**
• Vulnerabilities found: [count by severity]
• Vulnerabilities fixed: [count]
• Outstanding: [count]
• **Authentication/Authorization:**
• Auth changes made: [description]
• Security issues found: [list]
• IDOR vulnerabilities: [count and fixes]
• **Data Privacy:**
• PII handling: [assessment]
• Privacy concerns raised: [list]
• GDPR/compliance considerations: [notes]
• **Compliance Requirements:**
• Requirements met: [list]
• Requirements missed: [list]
• Compliance debt: [items]
• **Security Best Practices:**
• Practices followed: [list]
• Practices violated: [list with remediation]
• Security reviews conducted: [count]

Track 4 - Product & UX

**Focus:** Feature delivery and user experience

**Analyze:**

• **Feature Completeness:**
• Features fully delivered: [count]
• Features partially delivered: [count]
• Features cut: [count with rationale]
• **Acceptance Criteria:**
• Criteria met: [%]
• Criteria requiring follow-up: [list]
• **User Story Quality:**
• Well-defined stories: [%]
• Stories requiring significant clarification: [count]
• Improvement recommendations: [list]
• **UX/UI Consistency:**
• Design system adherence: [assessment]
• Inconsistencies found: [list]
• New UI patterns created: [list]
• **Accessibility:**
• WCAG compliance: [level