This rule helps Codex use time and resources efficiently while completing the requested work. It checks progress, diagnoses recurring problems, and verifies workflow improvements. Required checks, correctness, and scope remain intact.
The rule
## Workflow Efficiency
- Reduce time and usage without sacrificing scope, correctness, completed work, or required verification.
- Keep process overhead proportionate to remaining cost.
- Maintain existing context: completed and remaining work, blockers, reusable results, scope, compatibility evidence, and completion conditions.
- Update plans for changed instructions, superseded checks, and coverage gaps.
- At task start and major boundaries, check available usage, progress, elapsed time, and remaining work.
- Assess progress without usage data; usage declines alone do not prove waste.
- Review methods when failures recur, progress slows, or substantial work remains.
- Confirm prerequisites before costly work.
- Respect dependencies; otherwise prioritize recent failures or uncertain affected checks that can expose failure sooner.
- Refresh verification and other workflow records whenever inputs change.
- Reuse valid results only with unchanged relevant inputs.
- For any workflow, diagnose changed inputs or failed checks, then resume at the earliest affected step.
- Make only authorized corrections; rerun only checks needing new evidence and complete all remaining required checks.
- Report unresolved blockers without expanding scope or claiming completion.
- Before costly reruns, diagnose recurring problems; establish why prior results are insufficient and what new evidence is possible.
- Prefer completion notifications or bounded waits for unchanged work.
- Lengthen safe waits when repeated checks show no change.
- When waiting, preserve responsiveness, required updates, and intervention opportunities.
- Stop unjustified optimization and continue the task.
- Report completion risks early.
- Never silently reduce scope or required checks.
- Give ordinary updates for routine changes; omit unchanged status.
### Costly verification
1. Identify required checks, prerequisites, and success criteria for the current scope.
2. Incorporate relevant changes and confirm prerequisites before costly work.
3. Use isolated snapshots for inputs concurrent work could change; record base revision, selected changes, dependencies, and verification limits.
4. Record current inputs, pending changes, prerequisites, and available targeted-check results before costly verification.
5. Complete prerequisite reviews and checks before full validation.
6. Update the verification record with prerequisite-check results.
7. After prerequisites pass, run remaining required validation in dependency order.
8. Report verification results as required under Testing.
### Method improvements
1. Define the problem, current behavior, success criteria, and a bounded proposed change.
2. Use evidence to compare expected savings against investigation, change, and verification costs.
3. Before material method changes, use the notice below; proceed unless approval is required.
4. Apply worthwhile authorized improvements; bound uncertain experiments.
5. At the next relevant checkpoint, collect comparable evidence and verification results.
6. Compare observed effects with expected benefits; label estimates and report verification results in an existing update.
7. Use that evidence to decide whether to keep, adjust, or safely revert the change.
```markdown
### Workflow Improvement
- **Finding:** [Issue and evidence.]
- **Change:** [Adjustment.]
- **Expected benefit:** [Likely benefit, material added cost, and a proportionate outcome check.]
```