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/minimal-skill-criteria.md

View on GitHub
# Criteria for Extracting a Tiny Skill During Retrospective

The bar for creating a new skill file from a retrospective is intentionally high.

## Must Meet All of These

- The pattern appeared in at least two meaningfully different sessions in the review window (or one extremely high-cost incident).
- Encoding it as a small skill would have saved the user noticeable time, context, or corrections.
- The skill is small and focused (ideally under 80–100 lines when first created).
- It has a clear, natural trigger phrase the user is likely to say or that Codex can reliably recognize.
- It is more valuable as a standalone file than as a short section in AGENTS.md.

## Should Usually Be Rejected If

- It only saves one or two minor steps.
- It is very specific to a single project or temporary situation.
- It duplicates logic that already exists in AGENTS.md or another skill.
- It would require frequent updates (better to keep in AGENTS.md for now).
- The main value is "reminding Codex of something" rather than providing a reusable procedure or checklist.

## Good Examples of Tiny Skills Worth Extracting

- A specific debugging ritual for a tricky class of production incidents in one service.
- A strict code review checklist for security-sensitive changes that the team cares about.
- A reliable way to produce high-quality handoff documents for a particular type of long-running work.
- A pattern for safely introducing a new database migration in this specific stack.

## Anti-Examples

- "Be more careful with error handling" → too vague.
- A 300-line "perfect Go web service generator" → way too big for a retrospective extraction.
- Something that only applied to last week's incident.

## Final Test

After writing the tiny skill, ask: "If I had this skill two weeks ago, would at least one of the painful sessions in this retrospective have gone clearly better?"

If the honest answer is no or "maybe a little", do not create the file. Put the insight in AGENTS.md instead.
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