Hand a writer a brief they can start from without a meeting.

“How do I brief a writer so they can start without three meetings first?”

Turns a keyword or topic plus an audience into a writer-ready brief that kills the back-and-forth.

FIND MORE PIPELINEEASY✓ APPROVED 4/4
EXAMPLE PROMPTS
>Write a content brief on [topic] for [audience]
>Outline a post that beats what already ranks for [keyword]
>What questions must this piece answer, and which internal links should go in?
ABOUT THIS SKILL

What this skill does

Takes a topic and an audience and hands your writer a brief they can start from cold: what the reader is actually trying to do, the angle that beats what already ranks, a section-by-section outline, the exact questions the piece must answer, the internal links to weave in, and the single call to action at the end. It removes the "what did you want here again" round trip.

Inputs

  • Works today with: a keyword or topic, the audience it is for, and the goal of the piece. Paste any competing URLs you want to beat and the skill will position against them.
  • More powerful connected to a search console: it sees the real questions people ask around the topic, so the must-cover list is theirs, not invented.
  • Sharper with a web-analytics tool: it sees which of your existing posts earn attention, so the internal links point to pages that convert.
  • Sharper with a CMS: it can pull your live URLs and pick real internal-link targets instead of placeholders.

How it works

  1. 1
    Search intent

    Name what the reader is trying to do: learn, compare, decide, or fix. Everything else in the brief serves that. The skill flags a topic that mixes two intents and recommends splitting it.

  2. 2
    Angle

    The one take that makes this piece worth reading over the results already ranking. Not "a guide to X," but the specific frame, contrarian, more practical, more current, that earns the click. The skill grounds the angle against the competing URLs you paste.

  3. 3
    Outline

    A section-by-section skeleton with headers, in the order the reader needs them. Intro promises the payoff, body delivers it, each header is a step or a question, not a vague label.

  4. 4
    Must-cover questions

    The specific questions the piece has to answer to be complete and to be quotable by an answer engine. Pulled from real related queries when a search console is connected, drawn from the topic when it is not.

  5. 5
    Internal links

    Named target pages to link to, with suggested anchor text, so the piece pulls its weight in your site's structure. Real URLs when a CMS is connected, labeled placeholders when not.

  6. 6
    The CTA

    One call to action, matched to the GOAL and the intent. A "learn" piece earns a subscribe, not a demo. One ask, not five.

Output format

CONTENT BRIEF · topic: "cold email deliverability" · audience: founders

Intent:  fix (they have a problem now)
Angle:   Not "deliverability 101." The 5 settings founders miss before
         they blame the copy. Practical, do-it-today.
Goal:    subscribe -> newsletter

Outline:
  H1  Why your cold email lands in spam (and it is not the subject line)
  H2  Authenticate the domain (SPF, DKIM, DMARC) in plain English
  H2  Warm the inbox before you send at volume
  H2  The volume ceiling nobody tells you about
  H2  A 5-minute pre-send checklist

Must-cover questions:
  - What actually triggers a spam filter on cold email?
  - How long does inbox warming take?
  - How many sends per day is safe on a new domain?

Internal links:
  -> /guide/domain-setup      anchor: "authenticate your domain"
  -> /guide/inbox-warming     anchor: "warm the inbox"  (placeholder)

CTA: "Get the pre-send checklist" -> newsletter subscribe

Next: connect a search console to replace assumed questions with real ones.

Tips

  • One primary intent per brief. Mixed intent is flagged and split.
  • Every must-cover question is answerable, never filler to pad length.
  • Internal links are real URLs when a source is connected, and clearly labeled placeholders when not. No invented links.
  • One CTA, matched to intent. No stacking asks.
RELATED SKILLS
ALL FIND MORE PIPELINE SKILLS →