Skip to content

majiayu000/spellbook / skills/codex-fluent

codex-fluent

Verified

Use when Codex feels slow, bloated, or heavy after heavy use. Provides safe session hygiene, archive strategy, and handoff discipline to keep daily Codex usage responsive and low-friction. Always pairs with comprehensive handoffs before archiving active work.

references/examples/handoff-quality-example.md

View on GitHub
# Example of a High-Quality Handoff (Shortened)

(This is what good handoffs produced with `codex-fluent` tend to look like.)

**Project:** Internal billing service refactor  
**Date:** 2026-05-12

## Executive Summary
We were extracting the billing calculation logic into a dedicated service with proper idempotency and retry semantics. The core happy path + two main failure modes are implemented and tested. The remaining work is around partial failure compensation and observability.

## Key Decisions
- Use event-sourced ledger for all money movements (decided after comparing with outbox pattern).
- All compensation must be explicit and logged; no implicit rollback.
- Idempotency keys are required on every public mutation.

## Current State
- `internal/billing/ledger.go` — the new event source, well tested
- `internal/billing/calculator.go` — pure functions + property tests
- API handlers still call the old monolith code in some paths (flagged for next step)

## Next 5 Steps (Prioritized)
1. Implement the two compensation flows for the "payment succeeded but downstream failed" case.
2. Add structured logging + trace IDs across the new service.
3. Wire the new service behind a feature flag in staging.
4. Write the migration script for historical ledger entries (read-only first).
5. ...

## Constraints & Style
- Prefer early returns and small functions in this package.
- All money values must go through the `Money` type (never raw int64 in business logic).
- Do not touch the legacy `billing_v1` package unless explicitly asked.

## Reactivation Prompt
```
Read docs/codex-handoffs/2026-05-12-billing-service.md.

Explore the current state of the repo, especially the billing directory.

Continue from the "Next 5 Steps" section. Start by confirming the current status of step 1.
```
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: 471kUpdated 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