The BloomBridge AI Starter Kit

Help me write a [type of document: email / memo / proposal / announcement].
Audience: [who will read it].
Goal: [what I want them to know or do after reading].
Tone: [warm / formal / direct / encouraging].
Here are my rough notes: [paste your notes, even messy ones].
Write a first draft under [length, e.g. 200 words]. Where you had to guess at a fact or detail, mark it in [brackets] so I can fix it before sending.

Summarize the text below for [audience, e.g. a busy director] who needs it in order to [decision or action, e.g. decide whether to attend a meeting about it].
Give me:
1. A three-sentence overview.
2. The five most important points as bullets.
3. Anything that looks like a deadline, a risk, or an open question.
Text: [paste the document]

I have a meeting about [topic] with [who is attending and their roles]. My goal for the meeting is [what a good outcome looks like].
Based on the background below, give me:
- A one-paragraph briefing I can read in 60 seconds.
- Five smart questions I should ask.
- The objections I'm most likely to hear and a fair response to each.
- One thing I should not raise cold in this meeting.
Background: [paste notes, emails, or agenda]

Below are emails I need to work through. For each one:
1. Give me the gist in one line.
2. Sort it: urgent / this week / can wait / no reply needed.
3. If it can be answered in two sentences or fewer, draft that reply.
Important: never invent a commitment, date, or fact on my behalf — write [CHECK] wherever you're unsure.
Emails: [paste the emails, with names removed if needed]

Help me turn this goal into a workable plan: [describe the goal].
My constraints: [time available, budget, people who can help].
Deadline: [date, if there is one].
Give me:
- Milestones by week, working backward from the deadline.
- The first three concrete actions I can take this week.
- The riskiest assumption in this plan, and one cheap way to test it early.

Explain [concept, term, or technology] to me. I'm a capable professional in [your field] who has simply never needed this before — so no jargon, and don't oversimplify either.
Structure it as:
1. A real-world analogy.
2. A plain one-paragraph definition.
3. One concrete example of how it would show up in my kind of work.
4. The three most common misunderstandings about it.

I need ideas for [the challenge, e.g. improving onboarding for new hires].
Context: [what's been tried, what's off the table, who it's for].
Give me 15 ideas in three sets:
- Five safe, proven approaches.
- Five creative twists on the obvious.
- Five that sound impractical but might spark something better.
Then pick the two you'd bet on and give one sentence each on the very first step.

Act as a thoughtful, candid reviewer — not a cheerleader. Here is my draft: [paste it].
The audience is [who], and the goal is [what it needs to achieve].
Do not rewrite it. Instead tell me:
1. What's genuinely working.
2. The three highest-impact improvements, in priority order.
3. Any spot where a reader might get confused, bored, or put off.
Finish by asking me one question that would make the next round of feedback better.

I'm going to describe, in plain words, a process I do at work. Turn it into clear documentation a brand-new teammate could follow without asking me anything:
- What they need before starting (access, files, tools).
- Numbered step-by-step instructions.
- Common mistakes and how to avoid them.
- When and where to ask for help.
If any step seems to be missing or ambiguous, ask me about it before finalizing.
Here's the process: [describe it the way you'd explain it out loud]

I need to learn [tool or software] well enough to [the specific thing you must be able to do] by [when].
What I already know: [related tools or skills you have].
Build me a five-day learning plan at 20 minutes a day:
- One tiny hands-on task per day, in increasing difficulty.
- Each day, one way to check that I actually learned it.
- The two or three features most people waste time on, so I can skip them for now.