Bots that poke holes in a plan before it's approved #83

A design doc or technical plan gets written, reviewed by a few people who are busy, and approved. The assumptions it rests on - that a dependency will behave a certain way, that a migration is reversible, that load will stay in a certain range - rarely get stress-tested before the team commits engineering time to building it.

A gitbot version would read the plan the way a skeptical reviewer does: pushing on what happens if each assumption is wrong, what's untested, and what point nobody in the room thought to raise, before the decision is locked in.

New here? gitbot runs Claude Code, Codex or OpenCode as reusable bots on your own machine, with your logins and your files. You define a bot once, a name and a job in plain English, and run it in as many folders as you like.

npm install -g @gitbot-hq/gitbot
gitbot start

Built one for this? Finished bots go into this library, each listed under the GitHub account that built it. In GitBot, the share menu on a bot has a Publish to Marketplace option that opens the pull request to add it. Your instructions go in as written.

These stay open after the first bot lands. And yours doesn't need to be general: people install the bot that's built for the stack they're already on.