When should you use it?
- Your coding agent drifts on long tasks
- You plan better in chat than in the terminal
- You ship in numbered versions
Not for: Tiny one-off scripts; Teams with a formal spec process already
What do you need, and what do you get?
You need
- Chat project with your product notes
- Coding agent
- Version numbering scheme
You get
- Planned change list
- Prompt per task for the coding agent
- Version log
How does it work, step by step?
- Set up a planning projectKeep strategy, goals and product notes in one chat project.
- Agree the versionName the current version in both tools before starting work.
- Ask for the promptWhen a change is decided, have the planner write the coding prompt with scope and rules.
- Paste results backFeed the agent's summary or diff back so the planner checks it against the plan.
- Start fresh threadsOn a new version or when threads get sluggish, have the planner write a starter prompt for the new thread.
The prompt
Our own prompt, inspired by u/Lost-Application4693 on r/codex and written to work in ChatGPT and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
We are on version {version} of {product}. Goal for this version: {goal}. For the next task, {task}, write a prompt for my coding agent that states: scope, files likely touched, what must not change, tests to run, and the branch or worktree to use. When I paste back the agent's summary, check it against the plan and list anything missing.
Inspired by u/Lost-Application4693 on r/codex: Use ChatGPT as your Development and Engineering Partner. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Copy-paste loops hide mistakes if you stop reading the output.
- Mismatched version numbers lead to edits on the wrong branch.
Our take
Separate the thinking from the typing. This loop has the planning model write the coding agent's prompts and check its output, which is a simple way to keep a long build on plan. The shared version number is the detail that makes it work across many threads. We left out claims about replacing staff; the workflow stands on its own. Keep the version number in the first line of every prompt and every pasted result, so you can tell which thread is current after a break. Start fresh threads when the version bumps rather than overloading one chat. Agree environment and worktree rules once in the planning project. Cap how many coding sessions run from one plan before a human re-reads the plan file. Keep reading the coding agent's output yourself; copy-paste loops hide mistakes the moment you stop. Tiny scripts do not need this loop. Paste failures back with logs, not just summaries.
Where the time goes back: Less time writing and rewriting coding prompts, and fewer sessions that wander off scope.
FAQ
Why two tools?
Does it work with other agents?
Source and credit
Inspired by u/Lost-Application4693 on r/codex. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Use ChatGPT as your Development and Engineering Partner
- Creator
- u/Lost-Application4693 on r/codex
- Published on
- Original date
- Mar 19, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.