Project Planning
From idea to executable plan.
Plans are how requests turn into work the team can pick up.
You don't have to plan anything yourself to use Busy Bee. The chat input on the Work board accepts a one-line request and Queen Bee fills in the planning behind the scenes. But understanding how that planning happens, and how to influence it, is the difference between getting okay results and getting great ones.
What Queen Bee does
When you submit a request, Queen Bee runs a planning pass before any agent starts work:
- Scope: what kind of work is this? Marketing, research, code, design, ops?
- Decompose: does this need one task, or several? If several, in what order, with what dependencies?
- Route: for each task, who's the best agent? An assigned team member, a default specialist, or the generalist?
- Stage: if there are approval gates or risky steps, where should the human be looped in?
For simple requests this happens in milliseconds and you never see it. For complex requests, a feature launch, a multi-platform campaign, Queen Bee may surface the plan to you before running it, asking for confirmation or edits.
Where you can intervene
Three knobs the planner exposes:
- Pin an agent. Override Queen Bee's routing by assigning a task directly to a specific agent. Useful when you've got a preferred Writer or Researcher.
- Set requirements. Telling the planner "the output should be 500 words, in Markdown, with a headline and three bullet points" yields tighter deliverables than leaving the format open.
- Provide context. The more relevant background you attach to a task (a brief, a URL, a previous deliverable), the better the plan.
The pattern: minimal input gets a sensible default plan; richer input gets a tailored plan.