Task creation

The chat input handles 90% of task creation. The structured form handles the other 10%, when you want maximum control.

Most tasks in Busy Bee are born from a sentence typed into the chat input. You drop "draft a blog post about our new pricing" and Queen Bee fills in the agent, the priority, the requirements, the timing. That works for the common case. This page covers the underlying structure, every field that exists on a task, so you can wield the structured form when the common case isn't enough.

The fields

Every task has these fields. The ones with * are required.

Title * - short noun phrase. "Draft Q3 investor update."
Description * - full request prompt. The body of work in your own words.
Organization * - which workspace owns the task. Set automatically based on context.
Project - the project this task belongs to (optional; leave blank for standalone tasks).
Agent - explicit agent assignment. Leave blank to let Queen Bee route.
Agent type name - alternative to a specific agent. "Use any Researcher" picks an available one.
Priority - LOW, MEDIUM (default), HIGH, URGENT. Higher priority gets picked up first.
Requirements - structured shape of the deliverable: length, format, tone, anything else.
Context - structured background data: audience, topic, source URLs, links, exclusions.
Passes - how many iterations the agent should self-review. Default 1.
Due date - when the work needs to be done by. Surfaces on dashboards; doesn't enforce.
Scheduled at - when the work should start. See Scheduling.
Quality tier - budget (Kimi), standard (Sonnet), premium (Opus), claude-cli. Inherits from your plan and project defaults.
Workflow template - if set, the task becomes the trigger for the named workflow.

Two paths into the form

Chat input - fills title, description, and most of context inferentially. Best for one-offs.
Structured creation modal - exposes all fields explicitly. Best when you want tight control over format, agent, or schedule.

Writing a request that plans well

Five practices that improve the plans Queen Bee produces:

Lead with the deliverable. "I want a 500-word brief on X" plans better than "tell me about X."
Name the audience. "For a non-technical investor" or "for our engineering team" changes the work meaningfully.
Attach the source. A URL, a Notion page, a previous task. The planner uses it.
State the format. Markdown? Slide outline? Plain prose? Three bullets and a headline? Saying so up front saves an approval cycle.
Specify exclusions. "Don't mention competitors" or "skip the marketing fluff" reduces back-and-forth.

Where requests turn into tasks

The moment you submit, the task lands in the queue as PENDING. The daemon's task router picks it up within seconds, assigns the agent (or honors your explicit pick), and moves it to IN_PROGRESS. From there it's a normal task lifecycle, see Tasks for what happens next.

Building blocks, not boilerplate

You don't need to fill every field. Title and description are required; everything else is opt-in. A good rule of thumb: fill priority, requirements, and context when the work matters; lean on Queen Bee for everything else.

What's next

You now have the full picture of Project Management. Head over to Integrations to connect Busy Bee to the tools your team already uses, or Teams (Hives) to learn about pre-built agent squads.