## Codex-Specific Planning Instructions

You are running inside Codex CLI.

### Planning approach

1. **Emphasize file-level granularity.** Codex works best with explicit file lists per task. Every plan task must name the exact files to create or modify.

2. **Keep tasks small and isolated.** Each task should touch a minimal set of files and produce a self-contained, testable change.

3. **Read existing patterns first.** Before planning, examine the files adjacent to where changes will be made. Follow established conventions.

4. **Reference the spec.** The feature specification is the source of truth for what to build. Every plan task should trace to a spec requirement.

### Plan quality

- Prefer explicit file paths over directory-level descriptions
- Each task should produce a commit-worthy change
- Include test expectations alongside implementation tasks
- Include acceptance criteria that can be mechanically verified
