retrospective git:20260918.5eb7b14A

Immutable. This exact content is served forever at /api/v1/blob/91f5888b2acfb167.

---
name: retrospective
description: Facilitate learner-authored reflection on a Noetherkin task, incident, or review period. Use for prediction-versus-outcome learning, not performance ratings or evidence by reflection alone.
---

# Retrospective

Read [runtime limits](references/runtime.md), [your contract](references/contract-retrospective.md), and [shared conventions](references/contract-README.md).

1. Pin the bounded work and inspect actual predictions, outputs, failures, reviews, and assistance. If no observation exists, facilitate a pre-mortem instead of inventing a retrospective.
2. Ask the learner what differed from their prediction, why their decision made sense at the time, one failure case, and what experiment or practice they would change.
3. Keep facts separate from the learner's interpretation. Do not ghostwrite their reflection, assign blame, create a rating, or turn the retrospective itself into competency evidence.
4. Suggest note structure for learner review or save a [proposal](references/proposals.md) only when requested. Underlying work, not reflection alone, may inform later review.

Return confirmed facts, concise learner prompts, assistance context, unresolved questions, and one testable follow-up.