---
name: work-retro
description: "Retrospect on personal work across conversations, projects, domains, and shared practices; produce evidence-backed improvement proposals. Not repository mapping, task execution, or automatic rule changes."
---

# work retro

## Entry Gate

Own retrospective synthesis of an explicitly bounded work history. Accept a session,
time window, project set, domain, or all currently accessible history. Default to the
current session when no scope is supplied; do not silently substitute ten sessions.
Require accessible evidence and a named output audience. Missing history narrows the
coverage claim, not permission to read restricted stores.

## Route Map

| Request condition | Read | Result |
| --- | --- | --- |
| Review one session or broader personal workflow | [retrospective](references/retrospective.md) | Coverage ledger, findings, scoped proposals, and validation plan |
| Compare projects, conflicting practices, or existing guidance | [retrospective](references/retrospective.md) | Shared principle with local exceptions or an unresolved conflict |
| Need exact input/output fields or lifecycle decisions | [contract](references/contract.md) | Provenance-bound retrospective result |
| Validate a proposal or report its evidence limit | [validation](references/validation.md) | Fixed-basis checks and honest adoption recommendation |

## Invariants

- Keep observation, interpretation, proposal, and accepted practice distinct. A memory
  or prior assistant summary is a retrieval lead, not current execution proof.
- Cite the exact source for material findings; deduplicate mirrored records and count
  independent episodes, not repeated quotes. Preserve contradictions and later corrections.
- Shared lessons must state their applicable context and exceptions. Never export a
  project's local rule to every project merely because it appeared in one session.
- Read current owner guidance and checks before proposing new text or automation.
  Prefer a navigation pointer, existing check repair, or deletion over duplicate rules.
- Write only the requested retrospective artifact. Do not change source, persistent
  memory, global instructions, other Skills, task state, Git, accounts, or schedules.
  Proposed adoption and publication require their own authorized owner.
- Keep raw private history and identifying snippets out of public artifacts. Generalize
  or synthesize public cases; if safe publication cannot preserve meaning, stop that export.
- Never claim token, cost, time, or quality improvement without comparable measurements.

## Output Map

Return `work.retrospective.analyze` following the [contract](references/contract.md):
scope and cutoff, source coverage, evidence-qualified findings, ranked scoped proposals,
conflicts/deprecations, validation results or gaps, audience-safe artifact, and next action.
A no-finding result is valid. Partial access must remain visible in the final status.

## Reference Map

- Read [retrospective](references/retrospective.md) for collection, synthesis, and proposal selection.
- Read [contract](references/contract.md) when accepting evidence or composing the result.
- Read [validation](references/validation.md) for fixed-basis evaluation and adoption recommendations.
- Maintainers only: read [eval cases](references/eval-cases.md); do not load it during ordinary runtime.