Building your own
Turn a request you keep making into a saved, reusable playbook.
When you catch yourself asking for the same kind of work more than once, make it a playbook. You describe the job in plain language and Busy Bee drafts the steps; you save it, adjust it, and it's ready to run again.
Describe the job
Tell Busy Bee, in chat, what you want the playbook to accomplish — the outcome, and roughly how you'd break it up. You don't lay out the mechanics yourself; you describe the work and it drafts the structure.
What gets drafted
A playbook is a named, ordered set of stages. Each stage has:
- A name — the step, like "Research competitors" or "Write the draft."
- A role — which kind of teammate handles it (a writer, a researcher, a reviewer).
- Instructions — what that step should produce.
- An optional approval checkpoint — pause here and wait for your sign-off before continuing.
Stages run in order, each handing its work to the next. Add a checkpoint on any stage where you want to review before the work moves on; leave it off for steps that should run straight through.
Save, then refine
Give the playbook a name and description and it's saved to your organization for anyone on your team to run. Names have to be unique, so a new version won't quietly overwrite an existing one. Review the drafted stages, reorder or reword them, and add or drop approval checkpoints until it matches how you actually want the job done.
Send issues back to an earlier stage
A review stage can hand its findings back to the stage that should fix them — QA Testing back to Development, for example — and the work loops until the review passes, up to a limit you set (two rounds by default) before it stops for a person. The playbook editor doesn't show this setting yet. For now, ask Queen Bee in chat: "In my Ship It playbook, send QA Testing's issues back to Development." She can also copy any playbook, including the built-in ones, onto different roles, and read back exactly how each stage is set up.
Reuse and attach to a hive
Once saved, a playbook runs on demand — pick it, start from a prompt, and the work runs. The roles you named tell Busy Bee which hive members to route each stage to, so a playbook and a hive work together on every run. Any playbook can also be set to repeat on a schedule.
Where it fits
- Using playbooks — run one you've saved
- Hives — the team that carries out the stages
- Automation — run a playbook on a schedule
- Memory — how your team carries context between runs