Use a task frame
A task frame should include the desired outcome, current symptom, relevant files or commands, constraints, and acceptance criteria. If the task is exploratory, say that analysis should come before edits.
For example, instead of asking 'fix the site', say 'the site is currently a single-page React app; convert it into multiple crawlable content pages, keep TypeScript and Vite, and verify several routes in preview'.
- Goal: what should be true after the task.
- Context: files, URLs, logs, and prior decisions.
- Constraints: what must not change.
- Verification: commands and manual checks.
Ask for evidence when the answer matters
When Codex says a behavior exists, ask it to cite the source: file path, line, command output, documentation, or runtime response. Evidence is especially important for policy, deployment, security, and production behavior.
Evidence also helps catch mismatched assumptions. A route may look present in navigation but still be a hash anchor; a static site may look multi-page in the browser but still ship one identical HTML shell.
Make the final answer reviewable
Ask for a concise final report: changed files, behavior changed, verification run, and unresolved risks. This format is easier to audit than a narrative of every intermediate step.
For content work, ask Codex to distinguish sourced facts from editorial guidance. Product facts should trace to official documentation or inspected behavior; advice can be marked as implementation recommendation.