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?
- Bootstrap the systemCreate a designs folder, an index, a template and commands for new, status, explore, verify and close.
- Plan before buildingUse a planner session to load context and iterate on the design until the solution and files are clear.
- Annotate inlineFor complex designs, add marked comments in the file and ask the agent to resolve them.
- Hand finished designs to workersLet worker sessions implement only designs marked ready, one per window.
- 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.
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?
Why number every design?
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.