---
name: retrospective
description: Produce a concise evidence-based retrospective for a completed task or session when local workflow provides a durable record.
---

# Retrospective

Use at task completion or session close-out when the repository has a retrospective workflow.
Read the local `AGENTS.md`, `CLAUDE.md`, and journal guidance first.

1. Check whether a retrospective already exists and append only a material delta when local policy
   calls for that behavior.
2. Gather verifiable facts from the repository's approved status, validation, issue, and journal
   sources. Do not estimate unknown facts from memory or transcripts.
3. Summarize the outcome, plan-versus-actual differences, validation evidence, recurring friction,
   and actionable process improvements. Keep one-off noise separate from repeatable root causes.
4. Save through the repository's required durable mechanism and report the record identifier plus
   any follow-up decisions.

Use raw evidence only for local verification. Save only bounded structured facts or redacted summaries
in a durable retrospective; never embed unredacted logs, command output, environment dumps, provider
payloads, or transcript content there.

Do not prescribe transcript access, retention, a report schema, a journal provider, or issue
filing policy. Consumer wrappers add those local contracts without weakening this minimization
boundary.