Sprint Retrospective

Create a Sprint Retrospective tailored to your inputs.

Prompt template

You are a professional Agile coach. Generate a structured sprint retrospective document in Markdown for the following sprint.

Team: {{team_name}}
Sprint: {{sprint_label}}

What went well:
{{went_well}}

What didn't go well:
{{went_poorly}}

{{mood_section}}
{{notes_section}}

Generate a comprehensive retrospective document with the following sections:
1. Summary — a brief paragraph overview of the sprint
2. What Went Well — bullet points expanding on the positives
3. What Didn't Go Well — bullet points expanding on the challenges
4. Action Items (Prioritized) — concrete, assignable action items categorized as High/Medium/Low priority
5. Team Mood — a paragraph summarizing team sentiment{{team_mood_rating}}

Use clear Markdown formatting with headers, bullet points, and bold text where appropriate. Be specific and actionable.

Fill the 7 fields below to customize.

Customize before copy

Fill these — your prompt updates live.

Stays in your browser. Nothing sent anywhere — we don't run a server for this.

Team Name*{{team_name}}

Sprint Label*{{sprint_label}}

Went Well*{{went_well}}

Went Poorly*{{went_poorly}}

Mood Section*{{mood_section}}

Notes Section{{notes_section}}

Team Mood Rating*{{team_mood_rating}}

Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.

Sample

Example output

What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.

# Sprint Retrospective — Demo Team | Sprint 42

## Summary
Sprint 42 was a productive sprint with strong collaboration but some process friction around deployment pipelines. The team delivered 8 of 10 planned story points and maintained good communication throughout.

## What Went Well
- Clear sprint goals helped the team stay focused on priorities
- Pair programming sessions improved code quality significantly
- Daily standups were concise and informative
- Cross-team communication with design was excellent
- Automated test coverage increased from 72% to 81%

## What Didn't Go Well
- Deployment pipeline failures caused repeated delays (3 failed deploys)
- Two stories were blocked due to unclear acceptance criteria
- Technical debt in the authentication module slowed feature work
- On-call rotation burden was unevenly distributed

## Action Items (Prioritized)

### High Priority
1. **Fix deployment pipeline** — Assign @devops to investigate and resolve CI failures by next sprint (Owner: DevOps lead)
2. **Improve acceptance criteria process** — Product owner to provide written ACs before sprint planning (Owner: Product)

### Medium Priority
3. **Schedule tech debt sprint** — Allocate 20% of next sprint to authentication module cleanup (Owner: Engineering lead)
4. **Rebalance on-call rotation** — Update PagerDuty schedule to distribute load fairly (Owner: Scrum Master)

### Low Priority
5. **Document pair programming learnings** — Create a team wiki page with insights (Owner: T

Annual Report

Create a Annual Report tailored to your inputs.

Operations

Business Case

Create a Business Case tailored to your inputs.

Operations

Client Status Report

Create a Client Status Report tailored to your inputs.

Operations

Academic Recommendation

Generate a Academic Recommendation tailored to your inputs.

Other