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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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.
The line at the top of this page pins the label git:20260918.5eb7b14, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_jgjydyuqhluzl4br
GET https://markdownregistry.com/api/v1/resolve?ref=nanaagyei/noetherkin/retrospective
GET https://markdownregistry.com/api/v1/blob/91f5888b2acfb1676f4b93cb63c495af474c14ec78edf1700f1b943e41a32fe7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nanaagyei/noetherkin · skills/architecture/SKILL.md · Analyze Noetherkin system boundaries and architectural trade-offs from source-cited facts. Use for architecture…
nanaagyei/noetherkin · skills/benchmarks/SKILL.md · Design and interpret reproducible Noetherkin benchmarks with controlled workloads and raw results. Use for performance…
nanaagyei/noetherkin · skills/code-review/SKILL.md · Review one identified Noetherkin change revision for correctness, risk and maintainability against task criteria and…
nanaagyei/noetherkin · skills/codebase-map/SKILL.md · Guide a Noetherkin learner in creating or checking a source-cited codebase map. Use for orientation and request-path…
nanaagyei/noetherkin · skills/debug/SKILL.md · Debug a Noetherkin failure with hypotheses, predictions, and discriminating experiments. Use for causal investigation…
nanaagyei/noetherkin · skills/design-review/SKILL.md · Review an exact learner-authored Noetherkin design revision against its frozen task. Use for the team-lead design gate…
nanaagyei/noetherkin · skills/incident-response/SKILL.md · Facilitate or review a safely bounded Noetherkin incident exercise. Use for diagnosis, mitigation, communication, and…
nanaagyei/noetherkin · skills/onboarding/SKILL.md · Introduce a Noetherkin workspace, gather learner goals and constraints, and resume pending onboarding with a baseline…
nanaagyei/noetherkin · skills/peer-engineer/SKILL.md · Collaborate broadly with a Noetherkin learner on an investigation or interpreting a run. Use as the peer workflow…
striderza/opencodegamestudios · .agents/skills/retrospective/SKILL.md · Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces…
striderza/opencodegamestudios · .agents/modules/release/skills/retrospective/SKILL.md · Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces…
haabe/mycelium · plugins/mycelium/skills/retrospective/SKILL.md · Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.
rjmurillo/ai-agents · src/claude/skills/retrospective/SKILL.md · Extract learnings from a session or task through structured retrospective frameworks. Gathers evidence, runs Five Whys…
ariaxhan/kernel-claude · skills/retrospective/SKILL.md · Audit whether prior learnings actually fired, then install mechanisms for this run's recurrences. No finding without an…
furkantokkan/agent-foundry · plugins/agent-foundry/skills/retrospective/SKILL.md · Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces…
microsoft/amplifier-bundle-skills · skills/retrospective/SKILL.md · Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for…
gonimar/claude-web-studio · skills/retrospective/SKILL.md · Runs the sprint retrospective from artefacts — planned vs shipped, estimate vs actual (the calibration ratio the next…
