Skip to content

majiayu000/spellbook / skills/codex-retrospective

codex-retrospective

Verified

Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.

references/examples/good-retrospective-output.md

View on GitHub
# Example of a Good Retrospective Output (Sanitized)

**Window:** Last 18 days, focused on the new Go service work.

## Evidence Inventory

- Scope: new Go service work, last 18 days.
- Sources checked: current AGENTS.md, service-specific skills, local session summaries, and three Codex session files.
- Evidence handles: sessions from May 4, May 9, May 12, and May 15; AGENTS.md "Core Implementation Principles"; service money-movement skill.

## Retrospective Summary

- Repeatedly started implementation before fully clarifying the exact failure modes the user cared about most (happened in at least 3 sessions).
- Strong pattern: when the user said "make it robust", Codex defaulted to broad retries instead of the specific idempotency + compensation model preferred here.
- User had to re-explain the "Money type + no raw amounts" rule twice in different files.
- Excellent results when Codex first wrote a tiny state machine sketch before coding — this pattern is worth encoding.

## Proposed AGENTS.md Updates

**Location:** Under "Core Implementation Principles" (new bullet)

```diff
+ - When the user asks for something to be "robust", "safe", or "production ready" in this service, first explicitly list the 2-4 concrete failure modes we are optimizing for before writing any code. Do not assume broad retries or circuit breakers are the answer.
```

## Proposed Tiny Skill

**File:** `skills/go-service-idempotency.md`

(Full small skill with frontmatter for handling money movements with explicit compensation. Omitted here for brevity — it was 2 focused sections + 1 example.)

## Rationale

The three sessions on May 4, May 9, and May 15 all had the same pattern: Codex jumped into "add retry + backoff" while the actual requirement was explicit ledger entries + compensation handlers. The Money type issue appeared in the May 9 and May 15 threads.

The state machine sketch technique from the May 12 session produced the cleanest result with the least back-and-forth.

## Application Plan

1. Apply the AGENTS.md addition first (low risk).
2. Review the extracted skill together.
3. In the next similar task, explicitly invoke the new skill when relevant.
4. Re-run a short retrospective in 10 days focused only on this area to measure improvement.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall