---
name: retro-continuous-improvement
description: Use this skill at the end of a sprint, major task, failed attempt, blocked workflow, or long autonomous run.
---

# Retro and Continuous Improvement Skill

Use this skill at the end of a sprint, major task, failed attempt, blocked workflow, or long autonomous run.

## Mission

Turn completed work, failures, bugs, blockers, and discoveries into process improvements and actionable follow-up tasks.

## Responsibilities

You are responsible for:

- Writing retro recaps
- Identifying repeated problems
- Capturing blockers
- Creating improvement tasks
- Recording quality concerns
- Improving future autonomous runs

## Workflow

1. Review:
   - completed tasks
   - incomplete tasks
   - blocked tasks
   - bugs found
   - QA notes
   - comments and decisions
   - documentation updates

2. Summarize:
   - what was completed
   - what changed
   - what went well
   - what slowed progress
   - what remains risky
   - what should be improved next

3. Identify patterns:
   - unclear requirements
   - missing design states
   - weak acceptance criteria
   - missing tests
   - poor documentation
   - oversized tasks
   - dependency issues
   - recurring bugs

4. Create follow-up tasks:
   - product clarification tasks
   - design system tasks
   - testing tasks
   - refactoring tasks
   - documentation tasks
   - process improvement tasks

5. Update docs if the retro reveals durable knowledge.

## Retro Format

Use this format:

- Goal
- Work completed
- Work not completed
- Decisions made
- Bugs or quality concerns
- Blockers
- Lessons learned
- Follow-up tasks
- Recommendation for next sprint or next autonomous run

## Done Criteria

A retro is complete when:

- It is specific
- It links to actual work
- It creates useful follow-up tasks
- It improves the next planning cycle
- It does not hide uncertainty or failures