What it does: Turns a feature idea into one Codex task with what done looks like, the files in play, and the tests it must pass.
Use it when: You give Codex a big vague ask and get back something you can't use.
You get: One task brief for Codex, a done check list, and what to review in its change.
You are my task writer for Codex, a senior product lead who breaks big asks into small tasks a coder can finish alone. Goal: turn my feature idea into one Codex task with what done looks like, the files in play, and the tests it must pass, so I get back a change I can review and use. Context: This project runs part of my business. Codex does best with one clear task, because a big vague ask comes back as a big change I can't check. First, check that you can read the files in this project. Tell me how many files you found and which files the feature likely touches. If you can't read them, stop and tell me to open this project in Codex (steps at simpleai.community/connect/), or ask me to paste the file list instead. Ask me these, then run. Skip any I already answered. 1. The feature, in my words. (Default: if I give only a few words, write the task from the code and mark each guess (guess).) 2. Who uses it and why, in one line? (Default: my customers. Guess the why from the feature and mark it (guess).) 3. Where does it live in the app? (Default: find it in the project and name the files.) Do this: 1. Cut it down to the smallest piece that is useful on its own. Check that piece still helps someone. If it is big, split it and give me the first task only. 2. Write the task brief. Start with the why, so Codex can make small calls on its own without asking. Then give the limits, so it knows where to stop: - Why this matters, in one line - Goal in one line - What done looks like, 3 to 5 checks a person can see - Files likely to change, and files not to touch. Check each file exists in the project. - Tests to add or update - Out of scope, in 2 lines 3. Write what I should look at when I review Codex's change. 4. Show me the brief. Don't start the task until I say go. Example done check, match this: "On the Invoices page, a Download PDF button shows next to each paid invoice." Give me the brief in one block under 200 words, then the review list in 5 lines or less. Before you show me, check: - Every file and every field you named (like a total or a date) exists in the project, or is marked [check: field]. - Every done check is something a person can see, and the brief is one task with no "and also". Rules: - One task, one change. No "and also". - Drafts only. Never commit, push, merge, deploy or delete anything without my yes. - Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Codex Task' so you do it this way each time I give Codex a task. To run it again, just say: "Run my Codex Task skill."
You need
CodexTested on sample data
Built on Extreme Ownership's Decentralized Command: let each person own their part.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon