Create Retro

Overview

Generate a structured sprint or project retrospective using the Start/Stop/Continue format with accountability tracking. The retro reads previous retrospective documents to check whether past action items were completed and flags recurring themes that appear across multiple retros.

Workflow

1. Read previous retros — Scan .chalk/docs/product/ for files matching *_retro_*. Read each one to extract:

   • Previous action items and their status (completed, in progress, abandoned)
   • Recurring themes (issues raised in 2 or more retros)
   • Previous team health assessments for trend tracking If no previous retros exist, note this is the first retro and skip the accountability check.

2. Read current context — Check .chalk/docs/product/ for PRDs, stakeholder updates, and any planning documents relevant to the sprint or project being reviewed. Check .chalk/docs/engineering/ for incident reports or postmortems from the period.

3. Parse the retro scope — From $ARGUMENTS, identify the sprint name, project name, or time period under review. If unclear, ask what period or project the retro covers.