The most important thing when dealing with the “how to prepare the project root catalogue AGENTS.md” is not to remember a button, but to understand the operational boundary.
The subject is prone to error because the project rules are scattered in chats and the next task is easily missed. First, Codex knows what can be directly implemented and what must be stopped to confirm.
What can be confirmed from the official document is not the secret to the guaranteed result, but the conditions for running. Codex will read AGENTS.md or overwhelm the file from the global to the current project directory, the closer the rules of the directory will be placed in the group command.
Do not extend the full range of permissions at a time. Write common commands, cataloguing responsibilities, certification requirements and prohibition of changes in a short entry within control, then add tools or access.
At least one reverse check: Start from the root of the warehouse and have Codex summarize the rules that are loaded. If the evidence cannot be understood by another member, the context of the delivery is still missing.
Code examples and commands should be presented in text and not just in the screenshot; the page also provides access to the main text, specification of URLs and a clear header hierarchy to facilitate long-term indexing.
In order to enable the Codex project instructions to be reproduced by another member, the mission record contains at least four check points: REMO, SETTUP, TEST, RULES.
Two questions need to be answered at the same time: whether to “start from the root of the warehouse and let Codex sum up the load” and whether to “replicate a complete development document that would make it difficult to detect a key directive.” The former decides whether to continue, the latter decides to suspend, roll back or to supplement the authorization.
For long assignments, the phasing summary should refer to actual documents and tests rather than simply describe the work done. The evidence can be reviewed more valuable than the percentage of progress.
To facilitate team re-use, the repository submission, work catalogue, Codex version, profile and key commands can be saved in the task record.
Finally, do not ignore a person's judgement. Copying a complete development document makes key instructions difficult to detect. Codex can execute and authenticate, but it cannot be a substitute for the operator to determine the scope and risk tolerance.