Each playbook below gives you a proven setup for a specific document type — what to put in your project goal, how many rounds to expect, which AIs tend to shine, and what to watch out for. You don't have to follow these exactly, but they'll get you a strong result fast.
Add a Notes entry before Round 1 specifying the job description or posting URL — paste in the key requirements so the AIs can target their suggestions to that specific role. This makes a significant difference in relevance.
Paste the full job description into the Notes field before running Round 1. The AIs can't visit URLs, but they'll use the text directly to tune language and emphasis to match what the employer is looking for.
[PRICE] or [TIMELINE] for sensitive details — the AIs will work around them.Use the Notes field to tell the Builder the most important thing about the client — their pain point, their industry, or a key objection you need to pre-empt. This context shapes how the AIs frame every section.
RFPs often have strict page or word limits. Add the limit to your project goal so the AIs flag when sections are running long rather than just improving them in isolation.
Short documents often over-converge — the AIs may agree it's done after Round 2. That's fine. Hit Finish and export. Don't force extra rounds on something that's already working.
If the AIs keep wanting to add detail back in, add a note: "Do not expand the document — only tighten and clarify what's already here." Conflict resolution tends to go toward brevity when you're explicit about it.
WaxFrame outputs text — you'll copy this outline into your presentation tool. Use the exported document as your script and speaker notes layer. Having Perplexity in your hive is especially useful here since it can suggest real, current statistics to support your slides.
If the AIs start homogenising the voice into something bland, add a note describing the author's tone — even a few adjectives like "direct, slightly sarcastic, uses short sentences" will steer the hive back toward a distinct voice.
Ask the AIs to flag anything that reads as a "must-have" but could reasonably be "nice-to-have" — overly restrictive JDs reduce applicant quality by narrowing the pool too early. Use the Notes field to prompt this specifically.
Short documents like emails sometimes produce conflicts over single word choices. If a conflict feels trivial, use the Builder Decision path and let the Builder decide — or bypass it if you've already made your choice directly in the document.
If you want the recipe to stay true to a specific cuisine or tradition, mention it in your goal: "Keep this authentic to Southern Italian technique." This prevents the AIs from substituting ingredients or modernising methods you want to preserve.