Skip to content

Skill

Retro

gstack

Runs a look-back over a stretch of finished work - what shipped, what went sideways, what to change next time - turning recent experience into concrete process improvements. It faces backward at completed work, where idea pressure-testing, spec-writing and plan reviews all face forward at work not yet done.

Situations it fits

Three months after launch the team wants a focused meeting to list what went well, what failed, and one or two concrete changes for the next cycle.
Retro. Retro is the straightforward fit: it structures a short review of recent work to capture successes, failures, and specific actions to change how the team operates next. The other options are for earlier idea vetting, producing implementation artifacts, or auditing a plan, which don't match the post-launch review request.
A sprint just ended and releases landed late with recurring coordination problems; you want a structured session to identify what to change in how the team works next time.
Retro. retro is for analyzing a completed stretch of work to surface what went wrong and recommend process changes going forward. It focuses on past execution and team practices. The tempting alternative - a spec or plan review - would be misplaced because they address future designs or a written plan, not the run-of-play and team dynamics you just experienced.

3 scenarios in the bank answer to Retro. The rest are in the game.

Skills it gets confused with

These share a family with Retro, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Retro does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Retro is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.