When should you use it?
- Your backlog has several independent small features
- You avoid parallel work for fear of merge conflicts
- You are a solo developer
Not for: Changes that touch the same files heavily; Teams without code review
What do you need, and what do you get?
You need
- Repo
- A list of independent feature requests
You get
- One branch per feature
- Merged features that passed testing
How does it work, step by step?
- Pick independent tasksChoose features that touch different parts of the code.
- One thread eachStart a separate agent thread per feature with isolated worktrees.
- Offload the heavy oneSend the biggest refactor to a cloud run so your machine stays usable.
- Test separatelyCheck each branch on its own.
- Merge selectivelyMerge only what works and discard the rest.
The prompt
Our own prompt, inspired by Keith Rumjahn and written to work in ChatGPT and Claude Code. Values in lime are placeholders.
I have four independent features: [list]. For each, start in a separate worktree branch named feature/[short-name]. Implement only that feature, add or update tests, and run the test suite. When done, summarize the changes and any test failures for each branch. Do not merge anything into main.
Inspired by Keith Rumjahn: The complete guide to OpenAI Codex. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Features that overlap will still conflict at merge time.
- Four threads means four reviews; budget time for it.
Our take
Worktrees are an old git feature that suddenly matter when agents do the typing; isolation is what makes parallel work safe. The pattern pays off only when the tasks really are independent. Pick features that touch different parts of the code, give each its own thread and worktree, and the agents cannot trample each other's files while they work. Overlapping changes will still collide at merge time, so a quick look at which files each feature is likely to touch saves an afternoon of conflict resolution. Keith's habit of sending the heaviest refactor to a cloud run is worth borrowing too; it keeps your own machine usable while the others build. The cost people forget is review. Four threads produce four branches, and each one needs testing and reading on its own before it merges. Merge what works, throw away what does not, and do not let parallel speed become an excuse to skip the checks.
Where the time goes back: Waiting days between sequential features becomes one parallel afternoon plus reviews.
FAQ
What prevents conflicts?
What else does he automate?
Source and credit
Inspired by Keith Rumjahn. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- The complete guide to OpenAI Codex
- Creator
- Keith Rumjahn
- Published on
- rumjahn.substack.com (Substack)
- Original date
- Feb 6, 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 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.