---
name: prompt-brief-builder
description: "Fire when a user is about to ask an AI for a non-trivial piece of work and the request is vague. Triggers: build a brief, prompt brief, help me write a better prompt, clarify my ask, brief template, before I ask the AI."
---

Prompt Brief Builder

Advertising blurb: Turn "help me with this" into a short working brief covering outcome, audience, approved sources, constraints, boundaries and a review test, so your first draft starts closer to what you need.

Call to action: Fill the template once, ask your AI only the single missing detail that would change the result, then send the brief.

WHEN TO USE
Before asking an AI assistant to write, plan, summarize, analyze, design, or revise a non-trivial piece of work.

DO NOT USE IT AS
A promise of output quality. It reduces vague asks; it does not certify what the AI returns. Not legal, medical or financial advice.

DO NOT INCLUDE IN A BRIEF
1. Passwords, access tokens, private keys, government IDs, financial-account details, or unnecessary personal data.
2. Instructions to spend, publish, send, delete, change permissions, or act inside an account unless that action is separately authorized and the tool is really available.
3. A claim that the assistant has access to a file, app, account, or earlier decision unless you have checked.

INPUT
Your rough request, plus whatever facts you are allowed to share.

PROCESS
1. Outcome: what should exist at the end?
2. Audience: who will use or read it?
3. Source material: paste only needed, shareable facts, or attach approved references.
4. Constraints: length, voice, format, deadline, and things that must stay unchanged.
5. Boundaries: what the assistant must not do or claim.
6. Evidence standard: what needs a source, a calculation, or an explicit uncertainty label?
7. Review test: how will a person tell whether the answer is useful?
8. Requested output: exact sections, table, checklist, or file type.

OUTPUT
A filled brief using this template, ready to paste:
Task:
Outcome:
Audience:
Context and approved source material:
Constraints:
Must preserve:
Must not do or claim:
Evidence and freshness requirements:
Requested output format:
Review test:
If information is missing, ask this one question first:

QUALITY CHECK
Is the outcome observable? Is the audience named? Are source facts separated from assumptions? Are sensitive details left out or redacted? Are permissions and outside actions bounded? Does the review test describe usefulness rather than "make it good"?

REPAIR RULE
If the brief is still vague, do not add filler. Ask for the single missing detail with the largest effect on the result, then rebuild the brief.

WORKED EXAMPLE (fictional)
Rough request: "Help me with a welcome email for my bakery."
Task: Write a welcome email for new subscribers of Marigold Corner Bakery.
Outcome: One email, 120 to 160 words, that gets a first-time subscriber to book a Saturday tasting.
Audience: Local parents and office managers who signed up at the counter.
Context and approved source material: Open Tuesday to Sunday, tastings on Saturdays at 10 am, sign-up link supplied by me.
Constraints: Warm, plain voice. Subject line under 50 characters.
Must preserve: The tasting time and the phrase "small-batch".
Must not do or claim: No discounts, health claims, or ingredient promises I have not listed.
Evidence and freshness requirements: Use only the facts above. Mark anything else as an assumption.
Requested output format: Subject line, body, and one alternative subject line.
Review test: A friend can say what to do next after one read.
If information is missing, ask this one question first: Do you want the tasting to be free or paid?

The full upgrade is Creator Content Pro.

Version 1.1, 09-30-2026
David Solomon, Superstar AI, superstaragency.ai
Licensed for your personal and internal business use. Please do not resell or redistribute. Copyright 2026 David Solomon, Superstar AI.