How it works

You don't prompt Busy Bee — you delegate to it. Describe an outcome, and a team that already knows the job runs it end to end, on real machines, then hands it back for your sign-off.

The four building blocks

Busy Bee stacks four layers, smallest to largest:

• Features — what the platform can do: operate a computer, write and run code, research the web, generate images, query your data.
• Workflows — the steps: a set procedure that chains features together (research → outline → draft → edit).
• Playbooks — a workflow with a head start: it begins from a real scaffold — a doc, spreadsheet, or app — so the first pass lands closer. Playbooks are what you actually pick and run.
• Hives — a team for a domain (marketing, sales, research, ops), stocked with the playbooks that domain runs.

Features compose into workflows, workflows become playbooks, playbooks staff a hive. That's the whole system.

Getting something done

Two ways in:

1. Pick an outcome. Choose a hive, then a playbook, adjust the prompt, and send — you start from a scaffold, not a blank box.
2. Just ask. Type or say what you want; it routes to the right team.

Either way, the work runs as tasks you can follow live — and nothing ships without your approval.

Where to go next

• Features — everything the platform can do
• Playbooks — how starting from a scaffold gets you a better first pass
• Hives — the pre-built teams, and building your own