Retrospective update skill
Use this skill when Codex or another agent repeats a mistake, violates workflow expectations, or creates avoidable review friction.
Retrospective questions
- What happened?
- What was the expected behavior?
- What existing instruction, if any, should have prevented it?
- Was the failure caused by missing context, ambiguous instruction, absent verification, tool limitation, or judgment error?
- Is the fix universal, project-specific, subsystem-specific, workflow-specific, or deterministic?
- Where should the fix live?
Placement guide
- Home
~/.codex/AGENTS.md: durable personal default across repos.
- Project
AGENTS.md: shared repo standard, command, convention, protected seam, artifact path.
- Nested
AGENTS.md: local subsystem rule.
- Skill: reusable workflow that should load only when needed.
- Hook: deterministic guardrail or lifecycle check.
- Config: sandbox, approval, model, MCP, agents, feature flags.
- Test/CI/lint: enforceable project behavior.
Output
Produce a concise recommendation:
# Retrospective: <failure>
## Failure observed
## Root cause hypothesis
## Proposed durable fix
## Target surface
## Exact text or patch
## Why this surface
## Alternatives considered
## Verification / future check
Do not update instruction files automatically if the change is doctrine-bearing or could affect many projects. Surface the proposed patch first.
Source: loganrooks/codex-uplift-kit — distributed by TomeVault.
1---2name: loganrooks-codex-uplift-kit-codex-retrospective-update3description: Retrospective update skill4---56# Retrospective update skill78Use this skill when Codex or another agent repeats a mistake, violates workflow expectations, or creates avoidable review friction.910## Retrospective questions11121. What happened?132. What was the expected behavior?143. What existing instruction, if any, should have prevented it?154. Was the failure caused by missing context, ambiguous instruction, absent verification, tool limitation, or judgment error?165. Is the fix universal, project-specific, subsystem-specific, workflow-specific, or deterministic?176. Where should the fix live?1819## Placement guide2021- Home `~/.codex/AGENTS.md`: durable personal default across repos.22- Project `AGENTS.md`: shared repo standard, command, convention, protected seam, artifact path.23- Nested `AGENTS.md`: local subsystem rule.24- Skill: reusable workflow that should load only when needed.25- Hook: deterministic guardrail or lifecycle check.26- Config: sandbox, approval, model, MCP, agents, feature flags.27- Test/CI/lint: enforceable project behavior.2829## Output3031Produce a concise recommendation:3233```markdown34# Retrospective: <failure>3536## Failure observed37## Root cause hypothesis38## Proposed durable fix39## Target surface40## Exact text or patch41## Why this surface42## Alternatives considered43## Verification / future check44```4546Do not update instruction files automatically if the change is doctrine-bearing or could affect many projects. Surface the proposed patch first.4748---49> Source: [loganrooks/codex-uplift-kit](https://github.com/loganrooks/codex-uplift-kit) — distributed by [TomeVault](https://tomevault.io).50<!-- tomevault:4.0:skill_md:2026-05-23 -->