Work shapes: how to actually work with BoB
The handful of repeatable shapes that get the most out of an AI fleet, whether you write code, run a business, or write.
Working with a fleet of models is a different skill than prompting one chatbot. It is not harder, it is just shaped differently. After a lot of hours, the same few shapes keep paying off. None of them are technical. They work whether you are shipping code, running a small business, or writing.
1. Describe the outcome, not the steps
Tell BoB what you want to be true when it is done, not how to do it. “A page where customers pick a date and pay a deposit” beats a list of instructions. BoB is built to figure out the how, and to ask when the how is ambiguous. Steer the destination, let the fleet find the road.
2. Let it ask first
The most useful minute is the conversation before any work starts. BoB asks the questions a good contractor would: what matters, what does not, where the edges are. Answer those honestly and you skip a whole round of “that is not what I meant.” Rushing past the questions is the most common way to get the wrong thing fast.
3. Make it show its work
Cheap models are fine when they are checked, and dangerous when they are trusted. Ask for the source. Ask what it verified. BoB is built to surface that by default, a claim with the source it came from, a build with the test that proves it runs. When something cannot be verified, you want to see “unknown,” not a confident guess. Treat “I could not confirm this” as a feature.
4. Run a council on the hard calls
For a decision that matters, do not take one model’s first answer. Let several voices argue it out and hand you the version that survived scrutiny. Design choices, naming, a tricky tradeoff, a piece of writing you care about: these are where a council beats a single opinion. Save it for the calls worth the extra minutes.
5. Keep one project, let memory compound
BoB gets better at your work the longer you stay in one place. It remembers your decisions, your preferences, and the way you like things done, then adapts. Spreading the same project across ten fresh chats throws that away. Give it continuity and it stops re-learning you every session.
6. Fit it to your tools, not the other way around
You do not have to adopt a new system. If you live in Claude Code, drive BoB from there. If you have your own agent or platform, point it at BoB or build BoB in as a layer. The goal is to add a capable, verifying teammate to the setup you already have, not to make you move in.
These shapes are the difference between “a clever demo” and “a teammate I rely on.” Start with the first three. The rest come naturally once the work is real.