Coding agents reviewing each other led to recursion hell — a simpler outcome-driven workflow
boringmarketer · x · 2026-09-05
The author shares a reusable prompt for simplifying your codebase's rules, skills, and verification.
- He first tried having coding agents review each other's work, which spiraled into a recursion rabbit hole: more abstractions, more minutiae, endless back-and-forth about how work should be done — while he still found missing pieces when testing 'finished' features.
- He examined systems like Superpowers and Compound Engineering, valuing their ideas (planning, delegation, review, verification, capturing lessons), but the hard part is deciding how much of each a given task needs.
- His new approach: describe a business outcome and let agents carry it through to something you can actually test and ship, keeping the workflow simple.
Related event: Developer tests business-outcome-driven prompts for coding agents(2 posts)→
More from coding & agent
- Dev: Writing a Deterministic Go-to-Rust Compiler Is Easier Than Having an LLM Do It — MarcJSchmidt · 2026-09-05
- Dev builds his own Cyprus real estate agent with 5 prompts in 20 minutes — marclou · 2026-09-05
- Dev lists six fixes agent harnesses urgently need, from auditability to cloud-first sessions — threepointone · 2026-09-05
- One string swap in PowerShell PSAISuite handles every new model drop — dfinke · 2026-09-05
- MCPay launches a testnet for per-call MCP billing, seeks server maintainers — TooDu0 · 2026-09-05
- ghost development stalls on omarchy: TTS library pegs CPU at 400%, works fine on macOS — BLUECOW009 · 2026-09-05