← Back to library

Let a chat model plan and write coding-agent prompts

u/Lost-Application4693, a business owner who builds software, uses a ChatGPT project as the planning partner and Codex as the builder, both on extended thinking. ChatGPT writes each Codex prompt and the rules for worktrees and environments; results get pasted back; both stay on a shared version number with fresh threads when versions change.

  • OutcomePlan features in a chat project, have it write the exact prompt for your coding agent, paste back the agent's output, and keep both on the same version number.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditu/Lost-Application4693 on r/codex
View original
Works with
ChatGPTCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Set up a planning projectKeep strategy, goals and product notes in one chat project.
  2. Agree the versionName the current version in both tools before starting work.
  3. Ask for the promptWhen a change is decided, have the planner write the coding prompt with scope and rules.
  4. Paste results backFeed the agent's summary or diff back so the planner checks it against the plan.
  5. 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)

Prompt4 variables
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?
The planner holds the bigger picture and the coding agent stays focused on one task.
Does it work with other agents?
Yes; the pattern applies to any chat model plus any coding agent.

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
Reddit
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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Build a first web app as a non-coder, one model per job

Split a weekend app build across tools: an app agent for the scaffold, one model for requirements, another for fixes, and expert review before charging anyone.

Credit: u/mrcsvlk on r/replit

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Give a work agent its own login, mailbox and diary

Run an autonomous helper like a junior employee by giving it a dedicated system user, an email address and plain-text memory files it maintains itself.

Credit: mike_hearn on Hacker News

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Plan App Store review time for an AI-built app

Draft the store-release checklist (account, signing, listing text, images, plan names) early, because review rounds can take longer than coding.

Credit: u/Adventurous-Win-1489 on r/replit

Under an hour
Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+