Feature implementation workflow
Start by asking Codex to identify the existing pattern for the feature area. It should find similar components, API calls, tests, and styling conventions before writing new code.
Then define the smallest implementation slice that creates user-visible value. After editing, run the most relevant checks and review the result in the browser or tests.
Migration workflow
For migrations, ask Codex to inventory current usage first. The output should separate mechanical changes, behavior changes, and compatibility risks.
Large migrations should be split into reviewable passes: update types, update call sites, run tests, remove old paths, then document remaining exceptions.
- Avoid parallel old/new implementations unless there is a rollout reason.
- Track generated or mechanical files separately.
- Keep rollback assumptions explicit.
Documentation workflow
Documentation should describe current behavior, not only the diff. Ask Codex to cite the code or command output that supports technical claims.
For public content, separate product facts from editorial advice. Facts should trace to official docs or verified behavior; advice can be clearly marked as a usage recommendation.