What do I need to use Retrospective Analysis?

Sprint tickets: planned vs. completed; Carry-over tickets and reasons; Tickets reopened after closing; Any incidents or unplanned work; Sprint velocity vs. historical average.

Is Retrospective Analysis free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Retrospective Analysis

Q: How do I know the Retrospective Analysis output is good?

The skill verifies itself against its own quality checks: Each Start/Stop/Continue prompt names a specific behaviour, not a vague category; The recommended experiment is testable in one sprint; Carry-over analysis identifies the ticket type or cause, not just the count; Data observations don't assign blame — they describe patterns.

🟢 Production-Ready🕐 updated 2026-07-14 🔷 SkillSpec L3 pm-delivery

Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.

📚 Based on Agile Retrospectives — Derby & Larsen

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸Sprint tickets: planned vs. completed

▸Carry-over tickets and reasons — if known

▸Tickets reopened after closing — quality signal

▸Any incidents or unplanned work — scope creep signal

▸Sprint velocity vs. historical average — trend context

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Each Start/Stop/Continue prompt names a specific behaviour, not a vague category

✓The recommended experiment is testable in one sprint

✓Carry-over analysis identifies the ticket type or cause, not just the count

✓Data observations don't assign blame — they describe patterns

✓Velocity trend is mentioned in context (is this a one-off or a pattern?)

⚠️ What it refuses to do

Do not assign blame to individuals in the retrospective brief — observations must describe patterns, not people

Do not produce Start/Stop/Continue prompts that are vague categories — each must name a specific behaviour

Do not recommend an experiment that cannot be completed within one sprint — small, testable experiments only

Do not treat carry-over tickets as a velocity problem without first identifying the root cause category

Do not run the same retrospective format every sprint — vary the format to prevent engagement fatigue

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="retro-analysis"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Retrospective Analysis is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog