retrospective

Document lessons learned from completed delivery increments into memory artifacts.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill retrospective-haabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill retrospective-haabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured retrospective after completing a delivery increment or diamond, capturing learning for continuous improvement and preventing repeated mistakes.

Core Features & Use Cases

  • Guides teams through What Went Well, What Didn't Go Well, and What Should Change to surface actionable improvements.
  • Includes BVSSH Dimension Check to evaluate Better, Value, Sooner, Safer, and Happier outcomes for future work.
  • Outputs updates to memory artifacts and decision logs to institutionalize learning and track progress.

Quick Start

Run a retrospective immediately after a milestone to codify learnings and feed improvement artifacts.

Frequently Asked Questions about retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a retrospective to capture lessons learned from a delivery increment?

A structured retrospective identifies actionable lessons by guiding teams through what went well, what didn't, and what should change after a delivery increment to drive continuous improvement and prevent repeated mistakes.

What is a BVSSH check and how does it apply to continuous improvement?

A BVSSH check evaluates Better, Value, Sooner, Safer, and Happier outcomes during a retrospective to measure delivery effectiveness and guide actionable improvements for future work cycles.

How do I document delivery learnings to prevent repeated mistakes?

You document delivery learnings by running a post-milestone retrospective and outputting updates to memory artifacts and decision logs, ensuring institutional knowledge is captured for continuous improvement.

When should I run a post-milestone retrospective?

You should run a post-milestone retrospective immediately after completing a delivery increment or diamond to codify learnings while events are fresh and feed improvement artifacts.

Which memory artifacts need updates after a delivery retrospective?

A delivery retrospective requires updates to memory and decision artifacts including corrections.md, patterns.md, delivery-journal.md, and decision-log.md to institutionalize learning and track progress.

Can I use this retrospective process without any external dependencies?

Yes, the retrospective process operates without external dependencies, applying its internal BVSSH checks and memory artifact updates directly to your delivery workflow.