Submit
All skills
Skillintermediate

Sprint Retrospective Generator

**Sprint:** $ARGUMENTS

Claude Code Knowledge Pack7/10/2026

Overview

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
         ↓
/generate-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 achieved]
    • Accessibility issues: [count]
    • Improvements made: [list]
  • User Feedback:
    • Feedback integrated: [examples]
    • Feedback deferred: [examples with reasons]
  • Scope Creep:
    • Instances: [count]
    • Impact: [story points added]
    • Management: [how it was handled]

Track 5 - DevOps & Infrastructure

Focus: Operations, infrastructure, and deployment

Analyze:

  • CI/CD Pipeline:
    • Pipeline stability: [%]
    • Build failures: [count and causes]
    • Average build time: [minutes]
    • Deployment frequency: [count]
  • Environment Configuration:
    • Config changes: [count]
    • Config issues: [count and resolution]
    • Environment drift: [assessment]
  • Database Migrations:
    • Migrations created: [count]
    • Migration issues: [count]
    • Rollback scenarios tested: [Yes/No]
  • Docker/Container Management:
    • Container updates: [count]
    • Container issues: [count]
    • Image size optimization: [changes]
  • Monitoring & Logging:
    • New monitoring added: [description]
    • Logging effectiveness: [assessment]
    • Incidents detected: [count]
    • Alert noise: [assessment]
  • Performance Metrics:
    • API response times: [trend]
    • Database query performance: [trend]
    • Resource utilization: [analysis]

Track 6 - Process & Collaboration

Focus: Team dynamics and workflow effectiveness

Analyze:

  • Estimation Accuracy:
    • Planned points: [total]
    • Actual points: [total]
    • Variance: [%]
    • Accuracy by epic: [breakdown]
    • Patterns in over/under-estimation: [analysis]
  • Sprint Planning:
    • Planning session effectiveness: [assessment]
    • Requirements clarity: [score]
    • Dependency identification: [completeness]
  • Blocker Resolution:
    • Total blockers: [count]
    • Average resolution time: [days/hours]
    • Blocker categories: [breakdown]
    • Prevention opportunities: [list]
  • Documentation Quality:
    • Documentation created: [count pages]
    • Documentation updated: [count pages]
    • Doc clarity: [assessment]
    • Missing documentation: [gaps identified]
  • Cross-Team Dependencies:
    • Dependencies identified: [count]
    • Dependencies resolved: [count]
    • Dependencies causing delays: [count]
    • Coordination effectiveness: [assessment]
  • Communication:
    • Standups: [effectiveness assessment]
    • PR review turnaround: [average time]
    • Communication breakdowns: [count and impact]
    • Improvement areas: [list]
  • Parallel Execution:
    • Epics executed in parallel: [count]
    • Parallel execution effectiveness: [assessment]
    • Conflicts/merge issues: [count]
    • Coordination overhead: [assessment]

Phase 3: Synthesis & Report Generation

Combine insights from all tracks into a unified retrospective.

Report Structure

Sprint $ARGUMENTS Retrospective

Executive Summary

Sprint Overview

  • Duration: [start date] → [end date] ([X] days)
  • Epics Completed: [count]
  • Total Tickets: [count]
  • Total Story Points: [planned] → [actual] ([variance %])

Sprint Goals

  1. [Goal 1]: [Met/Partially Met/Not Met]
  2. [Goal 2]: [Met/Partially Met/Not Met]
  3. [Goal 3]: [Met/Partially Met/Not Met]

Key Metrics

MetricTargetActualStatus
Velocity[points][points][↑/↓/→]
Completion Rate[%][%][↑/↓/→]
Test Coverage90%[%][✓/✗]
Bug Count[target][actual][↑/↓/→]
Cycle Time[days][days][↑/↓/→]

Top 3 Wins

  1. [Win 1]: [Detailed description with specific examples from epics]
  2. [Win 2]: [Detailed description with specific examples from epics]
  3. [Win 3]: [Detailed description with specific examples from epics]

Top 3 Challenges

  1. [Challenge 1]: [Detailed description, impact, and affected epics]
  2. [Challenge 2]: [Detailed description, impact, and affected epics]
  3. [Challenge 3]: [Detailed description, impact, and affected epics]

Epic Breakdown

Completed Epics

EpicTicketsPointsDurationCoverageStatus
{Epic_Key}[count][pts][days][%][notes]

Epic Highlights

For each epic:

  • [{Epic_Key}]: {Epic_Title}
    • Objective: [brief description]
    • Outcome: [Met/Exceeded/Partial]
    • Key Deliverables: [list 2-3 major items]
    • Challenges: [1-2 key challenges]
    • Technical Debt: [items introduced]
    • Follow-up: [tickets created]

What Went Well

Group by track, with specific examples from epics:

Engineering Excellence

  • [Success 1]: [Description with epic references]
    • Example: In {Epic_Key}, [specific detail]
    • Impact: [quantifiable outcome]
  • [Success 2]: [Description with epic references]
    • Example: In {Epic_Key}, [specific detail]
    • Impact: [quantifiable outcome]

Quality Assurance

  • [Success 1]: [Description with epic references]
  • [Success 2]: [Description with epic references]

Security & Compliance

  • [Success 1]: [Description with epic references]
  • [Success 2]: [Description with epic references]

Product & UX

  • [Success 1]: [Description with epic references]
  • [Success 2]: [Description with epic references]

DevOps & Infrastructure

  • [Success 1]: [Description with epic references]
  • [Success 2]: [Description with epic references]

Process & Collaboration

  • [Success 1]: [Description with epic references]
  • [Success 2]: [Description with epic references]

What Needs Improvement

Group by track, with impact assessment:

Engineering Excellence

  • [Issue 1]: [Description]
    • Affected Epics: [{Epic_Key_1}], [{Epic_Key_2}]
    • Impact: [High/Medium/Low]
    • Impact Details: [quantifiable impact, e.g., "Added 3 days to timeline"]
    • Root Cause: [analysis]
    • Recommendation: [specific action]

Quality Assurance

  • [Issue 1]: [Description with impact assessment]
  • [Issue 2]: [Description with impact assessment]

Security & Compliance

  • [Issue 1]: [Description with impact assessment]
  • [Issue 2]: [Description with impact assessment]

Product & UX

  • [Issue 1]: [Description with impact assessment]
  • [Issue 2]: [Description with impact assessment]

DevOps & Infrastructure

  • [Issue 1]: [Description with impact assessment]
  • [Issue 2]: [Description with impact assessment]

Process & Collaboration

  • [Issue 1]: [Description with impact assessment]
  • [Issue 2]: [Description with impact assessment]

Action Items

Prioritized, specific, assignable recommendations with success criteria:

Critical (Address Next Sprint)

  1. [Action 1]:

    • Category: [Engineering/QA/Security/Product/DevOps/Process]
    • Description: [Clear, actionable description]
    • Owner: [Recommended owner/team]
    • Success Criteria: [Measurable outcome]
    • Effort: [Story points or time estimate]
    • Related Issues: [Link to specific problems from "What Needs Improvement"]

  2. [Action 2]:

    • [Same structure]

High Priority (Within 2-3 Sprints)

  1. [Action]: [Same structure]

Medium Priority (Nice to Have)

  1. [Action]: [Same structure]

Deferred (Revisit Later)

  1. [Action]: [Same structure with deferral reason]

Patterns & Insights

Technical Patterns to Replicate

  • [Pattern 1]: [Description]
    • Where Used: {Epic_Key} - [specific files/components]
    • Benefits: [what made it successful]
    • Recommendation: [how to apply elsewhere]

Anti-Patterns to Avoid

  • [Anti-Pattern 1]: [Description]
    • Where Observed: {Epic_Key} - [specific examples]
    • Problems Caused: [impact]
    • Prevention: [how to avoid in future]

Process Improvements

  • [Improvement 1]: [Specific recommendation]
    • Current State: [how it works now]
    • Proposed State: [how it should work]
    • Expected Benefit: [quantifiable improvement]

Tool/Workflow Recommendations

  • [Recommendation 1]: [Tool or workflow suggestion]
    • Problem It Solves: [specific pain point]
    • Implementation: [how to adopt]
    • Expected ROI: [time saved, quality improved, etc.]

Metrics Dashboard

Sprint Velocity

  • Planned Velocity: [points]
  • Actual Velocity: [points]
  • Variance: [+/- points] ([%])
  • Trend: [comparison to previous sprints]

Story Points Analysis

EpicPlannedActualVarianceReason for Variance
[{Epic_Key}][pts][pts][+/-][explanation]
Total[pts][pts][+/-]

Bug Metrics

  • Bugs Introduced: [count]
    • By epic: [breakdown]
    • By severity: [critical/high/medium/low]
  • Bugs Resolved: [count]
  • Net Change: [+/- count]
  • Escaped to Production: [count]
  • Average Resolution Time: [hours/days]

Cycle Time Analysis

  • **Av