---
name: evidence-retrospective
description: "Turn a recurring correction into a narrow improvement with an observable check. Use when reviewing repeated work, a failure or a correction to improve the next run."
---

# Evidence retrospective

## Inputs

The intended outcome, actual artifact, verification evidence and relevant prior corrections.

## Workflow

1. Compare the requested outcome with the actual result. Separate attempted actions, completed actions and verified outcomes.
2. Identify a concrete failure or friction point supported by the evidence.
3. Propose the smallest reusable correction. Do not promote one personal preference into a universal rule without context.
4. Define a check that would show improvement next time; avoid a score that merely rewards a longer checklist.
5. Record the finding locally when requested. Changes to shared instructions or automation require authorization.

## Deliver

A brief retrospective with the observed issue, proposed correction and next-run verification.

## Limits

Self-review is not independent evaluation. Usage frequency alone cannot establish quality or improvement. Follow the user's current request and the host application's permissions. This instruction file grants no tool access or extra authority.

## Example request

Review this deliverable against the request and evidence. Identify one reusable improvement and how we would verify it on the next run.

## Reuse

Original public workflow from Meow Creative Haus, version 1.0.0. You may use, modify and redistribute this file, including commercially, with this notice retained. Provided as-is without warranty. This permission applies to this file only, not to third-party tools, private configurations or source skills.