Here’s the short version: one prompt turns any vague client message into 10 structured questions organized by Creative Direction, Technical Requirements, and Success Criteria. No back-and-forth. No wasted kickoff calls.
Why Bad Briefs Are Actually Expensive
Not expensive in the dramatic “project failed” sense. Expensive in the slow, painful “three Zoom calls to figure out what shade of blue they want” sense.
Think about what that actually costs. A freelancer on a $2,000 logo project who spends four hours in revision cycles because the brief said “modern but classic” just cut their effective hourly rate in half. An agency team that kicks off a six-week campaign without locking down the target audience ends up rewriting half the copy after the first internal review. A developer who builds the wrong feature because the spec said “dashboard” without defining what data goes on it burns a full sprint and has to explain it to a client who swears they were clear.
The brief is where the damage is done. By the time you’re two weeks in and hearing “that’s not really what we had in mind,” the conversation about what the work should have been is already way more expensive than if you’d just asked the right questions upfront.
A prompt shared on r/PromptEngineering flips that dynamic. Instead of guessing what a client means, you paste their message into a structured extractor and get back the 10 most critical questions you need answered before touching anything.
The questions come out grouped into:
- 🎯 Creative Direction
- ⚙️ Technical Requirements
- ✅ Success Criteria
That structure matters. It forces clarity on both sides and makes sure scope, timeline, and output decisions are settled before a single pixel is placed or line of code is written. Clients who struggle to define what they want upfront often find it much easier to respond to specific, well-framed questions than to stare at a blank intake form. You’re not putting the burden on them to know what they don’t know. You’re making the gaps visible and giving them something to react to.
What Makes This Different
Most prompts are output generators. Give them a task, they produce something.
This one focuses on uncertainty reduction first. One commenter put it well: most project failures happen before the work starts. The brief is where the damage is done.
The typical approach is to just start working and course-correct later. Ask a few clarifying questions if something feels off, but mostly trust that you understood the assignment. That works fine until it doesn’t, and when it doesn’t, the cost is usually disproportionate to how small the original miscommunication was.
What this prompt does differently is treat ambiguity as the primary problem to solve before anything else. It doesn’t try to fill in the gaps with assumptions. It names the gaps. A question like “What does success look like at 90 days post-launch?” forces a client to think through something they may have never explicitly defined. A question like “Are there brand elements that are off-limits?” prevents a round of revisions that could have been avoided entirely.
This prompt does not guess. It surfaces what’s missing. That’s a fundamentally different way to use AI, and a smarter one.
Use Cases
This is useful for anyone who regularly deals with vague input:
- Freelancers getting one-paragraph project emails who need a professional intake process without a 45-minute discovery call for every small project
- Agency teams running project intake who want a consistent checklist that doesn’t depend on whoever happens to be leading the kickoff that week
- Developers handed wireframes with no context who need to surface assumptions about behavior, edge cases, and integration requirements before writing a line
- Consultants writing proposals who need to know what “improve our marketing” actually means in measurable terms before they can scope the work
- Anyone who has started work only to hear “that’s not what we meant” two weeks in
The prompt adapts based on the role you specify. A designer running it will surface questions about visual references, brand guidelines, and deliverable formats. A developer gets questions about tech stack, integrations, and edge case behavior. The structure stays consistent. The specifics shift to fit the work.
Prompt of the Day
“I have received a client brief that is missing key details. Based on what I share below, ask me the 10 most important questions a professional [designer/copywriter/developer/consultant] would need answered before starting this project. Prioritize questions that affect the final output, timeline, and scope. Group them by: Creative Direction, Technical Requirements, and Success Criteria. Brief: [paste client message here]”
Swap in your role, paste the message, run it before you start. When you get the 10 questions back, you don’t have to send all of them. Use the output as a thinking tool first. Some of them you can answer yourself based on context. Some reveal assumptions you were making without realizing it. The ones you genuinely don’t know the answer to are the ones worth sending to the client before the work begins. You’ll usually find that three or four sharp questions do more to set a project up for success than a full-hour kickoff call with a generic agenda.
Make It Part of Your Process
Save this where you will actually use it. Not in a folder called “prompts to try someday.” In your intake checklist, your proposal template, your first reply to new clients.
The best place for it depends on your workflow. If you use a project management tool, add it as a templated first task on every new project. If your client onboarding lives in Notion or a CRM, paste it into the intake step. If you just work from email, add it to a text expander shortcut so you can run it in 10 seconds without thinking about it. The goal is to make it automatic. Something you do before you do anything else, every time, without deciding whether it’s necessary on a case-by-case basis. That’s when habits actually stick.
A prompt sitting in a note app does nothing. One baked into your workflow saves hours every single project.
Frequently Asked Questions
Q: Why flag assumptions instead of just asking for what the client missed?
Because the client usually doesn’t realize what they haven’t said. When you tag assumptions, your team knows exactly what still needs confirmation before kickoff. This one change prevents hours of rework and scope-creep arguments later.
Q: How is this different from other “mega prompts” I’ve seen online?
Most prompts focus on generating better output faster. This one solves the opposite problem: reducing uncertainty. It prioritizes answering the questions that affect scope, timeline, and final outcome instead of just polishing a deliverable.
Q: Why do projects fail before the real work even starts?
Usually it’s silent miscommunication. The client thinks they explained clearly, the freelancer thinks they understood, but both are imagining different end results. A structured 10-question approach forces that gap to the surface early, when it’s cheap and easy to fix.
Q: How much time does this actually save?
Agencies typically waste 2-3 hours per project clarifying vague briefs through back-and-forth emails. A structured 10-question approach compresses that into one focused conversation, letting you confirm everything at once instead of discovering surprises mid-project.
PROJECT BRIEF EXTRACTOR- to Use when a client gives you a vague brief. Gets everything you need in one message.
by u/Honest-Network1104 in PromptEngineering