Phase 1: The Core Prompting Toolkit · 35 min · ChatGPT, Claude, or Gemini (any)

Be Specific, Give Context

Vague prompts get vague answers. Specific prompts with context get answers you can actually use.

Hiring signal: What changes when you use this: you get a usable first draft most of the time, in half the back-and-forth you used to need.

What you will learn

Rewrite vague prompts into specific ones by adding audience, purpose, length, tone, and constraints
Give the AI enough context to be useful — like briefing a smart new hire
Understand why specificity is the single biggest lever for first-pass output quality
Diagnose a vague prompt and identify exactly what specificity is missing

The Problem

90% of bad AI output comes from the same root cause: the prompt was vague. Not wrong — vague. The AI was given a general direction but no destination, so it produced something generally in the right area but not where you needed to be.

The fix is two moves: be specific about what you want, and give context so the AI understands why.

Being Specific

Specificity means answering these questions before the AI has to ask:

What exactly do you want? (not "an email" — "a 150-word follow-up email after a product demo")
Who is it for? (not "people" — "mid-level marketing managers at B2B SaaS companies")
What tone? (not "professional" — "professional but warm, like a colleague giving advice")
What length? (not "short" — "under 200 words" or "3-4 paragraphs")
What should it include? (not "the key points" — "the three features they asked about, pricing for the Pro tier, and a link to schedule a call")
What should it avoid? (not "don't be salesy" — "don't use the words 'revolutionary' or 'game-changing,' don't include attachments")

Let's see this in action:

Bad prompt:

Write a summary of our meeting

Good prompt:

Write a meeting summary email to send to 5 attendees. We had a 30-minute planning meeting about our Q3 product launch. Include: (1) the three decisions we made, (2) the two open questions, (3) who's responsible for each action item. Format as a short email with bullet points under each section. Keep it under 200 words. Tone: professional but casual, like a team update.

Same task. The first one could produce anything — a 5-paragraph essay, a one-line summary, a formal report. The second one can only produce one thing: exactly what you need.

Specificity is a checklist, not a talent
Being specific isn't about being a "good prompter." It's about running through a checklist: What? Who? Tone? Length? Include? Avoid? If you answer those six questions before you hit enter, your output quality jumps immediately. You don't need to be clever — you need to be complete.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers Giving Context, The Specificity Checklist, Your Practice Rep — plus a hands-on lab, quiz, and project artifact.

Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.