majiayu000/spellbook / skills/codex-retrospective
codex-retrospective
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| references/agents-md-update-rules.md | markdown | 1.4 KB |
| references/examples/good-retrospective-output.md | markdown | 2.2 KB |
| references/minimal-skill-criteria.md | markdown | 2.0 KB |
| references/retrospective-prompt.md | markdown | 3.3 KB |
references/agents-md-update-rules.md
View on GitHub# Rules for Updating AGENTS.md via Retrospective
These rules are enforced by the `codex-retrospective` skill.
## Acceptable Changes (Only These)
- Adding a short, specific "do X instead of Y" rule that directly addresses a repeated mistake.
- Adding or tightening a constraint in an existing section.
- Adding a small "preferred pattern" example (2–4 lines max) when the same pattern has been manually corrected multiple times.
- Updating the "Common Friction Points" or equivalent section with a newly observed pattern + mitigation.
- Adding a one-line pointer to a new tiny skill.
## Forbidden Changes
- Large rewrites or reorganizations of AGENTS.md.
- Adding vague or aspirational principles ("be more careful", "think harder").
- Adding rules based on single incidents (needs repetition or very high impact).
- Creating long lists of "don'ts".
- Changing the overall structure or voice of the document without strong justification.
## Quality Bar
A good retrospective update should make the *next* similar task noticeably smoother for both you and the user, with very little added cognitive load when reading AGENTS.md.
If a proposed change would make AGENTS.md feel heavier or more bureaucratic, reject it.
## After Applying
The user should be able to point to a specific recent painful session and say "because of this line we added, that would have gone better."
If they can't, the change was probably too weak or too broad.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |