---
name: working-session-retro
description: "Looks back at a working session to list what slowed the work down and the environment fixes that would help, most severe first. Use when a working session just ended and the friction in it should be turned into concrete setup or process fixes. Do not use for reviewing the code produced or reporting project status. Related topics: productivity, AI."
---

# Working Session Retro

Looks back at a working session to list what slowed the work down and the environment fixes that would help, most severe first.

## When to use

Use this skill when a working session just ended and the friction in it should be turned into concrete setup or process fixes. Do not use it for reviewing the code produced or reporting project status.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Walk the session and mark each moment that wasted time, with the cause.
3. Estimate the cost of each moment and how likely it is to recur.
4. Group causes into environment fixes and request-style fixes.
5. Rank fixes by cost times recurrence, most severe first.
6. Give a concrete small change for each top item and note what went well.

## Inputs

- **Session description** (longer free text)
- **Session log or notes** (longer free text)
- **Tools and setup** (longer free text)
- **Biggest annoyance** (free text, e.g. "What felt worst")
- **Scope** (choose one: This session only, Recurring patterns, Both)

## Output

A ranked list of friction points with cause, cost and a concrete fix each, followed by a short list of what to keep doing.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Working Session Retro

Review how this working session went and find what to fix.

- Session description: {{Session description}}
- Session log or notes: {{Session log or notes}}
- Tools and setup: {{Tools and setup}}
- Biggest annoyance: {{Biggest annoyance}}
- Scope: {{Scope}}

Walk through the session and mark each moment that cost time: repeated corrections, missing context, slow or flaky commands, unclear instructions, permission prompts, wrong assumptions and re-explaining. For each, record roughly how much time or effort it cost and what caused it. Group the causes into fixes to the environment, such as a script, a config line, a rules file or a note in the repo, and fixes to how the work was requested. Rank the fixes by severity, meaning cost times how often it will recur, most severe first. For each of the top items give a concrete, small change someone can make today. End with what went well and should be kept.

## Pitfalls

- Listing every small annoyance with equal weight, which hides the three that matter.
- Proposing a large tooling project when a one-line config change would remove the problem.
- Blaming the person instead of the missing context or setup.