← Back to library

Keep parallel coding agents on written design files

Manuel Schipper keeps four to eight Claude Code sessions open in tmux, named as planner, worker and backlog roles. Each piece of work begins as a numbered Markdown feature design covering the problem, alternatives weighed, the chosen approach, files affected and checks to run. Six slash commands move designs through stages, and every commit references its design number.

  • OutcomeKeep four to eight coding agents busy without losing track, by having them build only from finished written designs.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditManuel Schipper
View original
Works with
Claude Code

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

When should you use it?

  • You already run more than one coding agent at once
  • Agents drift because tasks start from a chat message
  • You want a changelog that writes itself

Not for: Tiny one-line fixes that do not merit a spec; Teams that need a heavyweight ticketing tool for compliance

What do you need, and what do you get?

You need

  • A repo with a project instructions file
  • A design template and index file
  • Custom slash commands for each lifecycle step

You get

  • Numbered design files moving through clear stages
  • Commits tagged with their design number
  • An index and changelog kept current

How does it work, step by step?

  1. Bootstrap the systemCreate a designs folder, an index, a template and commands for new, status, explore, verify and close.
  2. Plan before buildingUse a planner session to load context and iterate on the design until the solution and files are clear.
  3. Annotate inlineFor complex designs, add marked comments in the file and ask the agent to resolve them.
  4. Hand finished designs to workersLet worker sessions implement only designs marked ready, one per window.
  5. Verify and closeCheck against the design's verification steps, then archive it and update the changelog.

The prompt

Our own prompt, inspired by Manuel Schipper and written to work in Claude Code. Values in lime are placeholders.

Prompt0 variables
Create a feature design for: [idea]. Use the template in docs/features. Fill in: the problem, at least two candidate approaches with trade-offs, the chosen approach, an implementation plan naming each file to change, and concrete verification steps. Assign the next number and add it to the index as Design. Do not write any code yet. When I add inline notes starting with %%, address each one and remove it.

Inspired by Manuel Schipper: How I run 4–8 parallel coding agents with tmux and Markdown specs — Manuel Schipper. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Past about eight agents, the author finds his own decisions get worse.
  • A spec without verification steps lets agents call work done too early.

Our take

Manuel Schipper's setup is practical because it is low-tech. There are no orchestration frameworks or specialized subagents, just plain sessions with role names and a numbered design file that carries the coordination. Planner sessions think and write; worker sessions build only from a finished design, which prevents the common failure of an agent inventing scope mid-task. The verification section in each design is the detail to copy first, since it defines what done means before work starts and stops agents from declaring success after the code merely compiles. Referencing the design number in every commit creates a trail from any line of code back to the reasoning behind it, which is valuable months later. The author's honest ceiling of about eight parallel sessions is worth heeding. Beyond that, the bottleneck is your own reviewing and decision-making, not the tooling. Start with two sessions, one planner and one worker, and the design template, and add more only when you notice yourself waiting on agents rather than the reverse.

Where the time goes back: Planning is done once in writing, so each worker session starts from a clear brief instead of a fresh conversation.

FAQ

Does this need orchestration software?
No. The author uses plain sessions, Markdown files, shell aliases and slash commands.
Why number every design?
It links commits, the index and the changelog, so you can trace any change back to its reasoning.

Source and credit

Inspired by Manuel Schipper. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How I run 4–8 parallel coding agents with tmux and Markdown specs — Manuel Schipper
Creator
Manuel Schipper
Published on
schipper.ai
Original date
Feb 26, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
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 23, 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

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+
Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminWorkflow✓ AI dry run

Keep the check that decides 'done' out of your agent's reach

Stop a coding agent from grading its own homework: write the acceptance check yourself, lock it with a checksum so any edit fails the run, make it measure the finished result rather than read the agent's code, print a specific miss line for each defect, and still look at the result with human eyes before calling it done.

Credit: u/Stunning-Sherbet1853 on r/AI_Agents

Under an hour