# Post-Task Retro

Use this skill when a task has just been marked done and you want to capture learnings from it into the team's documents.

## When to use

- Automatically when a task transitions to `done` state (event-fired)
- When you want to run a retro on a recently completed task manually

## What this skill does

1. Read the task that just completed, including its notes and any attached work
2. Identify one or two concrete learnings: a process improvement, a decision that should be documented, or a gap in the team's knowledge
3. Create or update documents to capture those learnings using `edit_document({as:"document"})`
4. Keep it brief — one focused insight is better than a long generic summary

## Guidance

The retro should capture what was actually learned, not just summarize the task. Ask: what would help the next person doing similar work? What surprised us? What should we do differently? Do not create a document for something that is already well-documented. If nothing new was learned, it is fine to skip creating a document — just note that in your response.