Agile, Scrum & Product Specs
Target: Claude 3.7, Cursor, Windsurf, ChatGPT

Sprint Retrospective Action-Item Synthesizer

Synthesize team retro feedback into categorized themes, root causes (5 Whys), and SMART action items.

RetroScrumAgileContinuous ImprovementTeam

Interactive Prompt Playground

Customize Template Fields
Live replacement
{{RETRO_NOTES}}
{{SPRINT_CONTEXT}}
Rendered Prompt (Ready to paste)1319 characters
You are an Agile Coach and Facilitator conducting a Sprint Retrospective analysis.

Analyze this raw retrospective feedback from the engineering team:

Raw Retro Notes (What Went Well, What Didn't, Ideas):
```
What Went Well:
- Shipped new auth flow on time
- Great pairing between frontend and backend

What Went Wrong:
- CI builds took 35 minutes, blocking all PR merges on Thursday
- PR reviews sat for 2 days without feedback
- Staging environment was down for 6 hours due to database lock
- Requirements for billing webhook changed mid-sprint
```

Sprint Context & Goals: Sprint 24: Enterprise OAuth2 Launch & Stripe Billing Upgrade

Synthesize this feedback into an actionable continuous-improvement plan:
1. **Thematic Clustering**:
   - Group feedback into 3-4 recurring themes (e.g. CI Bottlenecks, PR Review Latency, Unclear Requirements, On-Call Firefighting).
2. **Root Cause Analysis (5 Whys)**:
   - Select the #1 biggest impediment and drill down to the systemic root cause using the 5 Whys framework.
3. **SMART Action Items (Specific, Measurable, Achievable, Relevant, Time-Bound)**:
   - Formulate 2-3 concrete experiments for the next sprint.
   - Assign clear ownership criteria and success metrics.
4. **Team Morale & Positives Summary**:
   - Highlight wins to celebrate during the sprint kickoff.

How to Use This Prompt

  1. Paste your team's sticky notes or raw retro comments.
  2. Get clustered themes, 5-Whys root cause analysis, and SMART action items for the next sprint.

Engineering Tips & Best Practices

  • Limit retro action items to a maximum of 2 per sprint so the team can focus and actually complete them.

What This Prompt Inspects

Key failure modes, design principles, and quality standards evaluated during execution.

Systemic Root Causes

Distinguishes one-off accidents from systemic process bottlenecks.

SMART Action Items

Avoids vague goals ('communicate better') in favor of actionable rules ('CI build under 10m with cache').

Team Motivation

Maintains balanced team engagement by celebrating shipped milestones.

SprintKit Workflow Integrations

Complementary interactive tools and workflows across SprintKit to accelerate your engineering process.

Related Prompts

Explore related developer prompts in this workflow domain.

All Prompts

Sprint Backlog Refinement & Technical Estimation Prompt

Conduct rigorous backlog refinement, identify hidden complexity, and estimate story points with Scrum poker criteria.

RefinementScrumEstimationAgile+1
3 variablesCustomize prompt

Epic Breakdown into Atomic Engineering Tasks

Break large product epics into vertically sliced, independently deployable Jira engineering subtasks.

JiraAgileScrumEngineering Management+1
2 variablesCustomize prompt

GitHub Actions CI/CD Pipeline & Caching Optimizer

Speed up slow GitHub Actions workflows with dependency caching, matrix parallelization, and security secrets.

GitHub ActionsCI/CDDevOpsCaching+1
3 variablesCustomize prompt