Content Brief Builder
When to Use This Skill
- Hiring a freelance writer and need to communicate expectations
- Outsourcing blog posts, articles, or web copy
- Building a content production system with multiple writers
- Getting inconsistent results from writers due to vague briefs
- Want to create a reusable brief template for recurring content
Core Principle
A GREAT BRIEF MAKES GREAT WRITING INEVITABLE. If you have to heavily edit the first draft, the brief failed — not the writer.
Workflow
Step 1: Define the Content
Ask the user:
- What type of content? (blog post, landing page, email, guide)
- What's the topic or working title?
- Who's the target reader?
- What's the primary keyword (for SEO)?
- What should the reader do after reading? (CTA)
- Any competing articles to beat or reference?
Minimum needed: questions 1, 2, and 3.
Step 2: Build the Brief
Include every section below:
1. Overview
- Content type and working title
- Target word count
- Due date (if applicable)
- Target keyword + 3-5 secondary keywords
2. Audience
- Who they are (role, experience level)
- What they already know about this topic
- What they need to learn or decide
3. Tone & Voice
- Brand voice description (e.g., "expert but approachable, like explaining to a smart friend")
- Words to use / words to avoid
- Point of view (first person, second person, third person)
4. Structure
- Required sections / outline
- H2 and H3 heading suggestions
- Specific elements to include (stats, quotes, examples, CTAs)
5. SEO Requirements
- Primary keyword and target placement (title, H1, first 100 words, H2s)
- Secondary keywords to weave in naturally
- Internal links to include
- Meta description guidance
6. Examples & References
- 2-3 links to articles that match the desired quality/style
- What's good about each reference (and what to do differently)
7. What NOT to Do
- Common mistakes for this topic
- Off-topic tangents to avoid
- Competitor claims to not repeat
8. Delivery Format
- File format (Google Doc, Markdown, Word)
- Image/visual requirements
- Header formatting expectations
Step 3: Deliver
Format the brief as a clean, shareable document the user can hand directly to a writer.
Examples
Example 1: Blog Post Brief for a SaaS Company
CONTENT BRIEF — Blog Post
TITLE: How to Choose Project Management Software for a Remote Team
WORD COUNT: 1,800-2,200 words
FORMAT: Google Doc with H2/H3 headers
TARGET AUDIENCE:
- Operations managers or founders at companies with 10-50 remote employees
- Currently using spreadsheets or basic tools (Trello, Asana free tier)
- Evaluating whether to upgrade to a paid PM tool
- Technical comfort: moderate (not developers, but not afraid of software)
TONE:
- Expert but conversational — like a knowledgeable friend giving advice
- Second person ("you") throughout
- Confident but not salesy — we're educating, not pitching
- DO use: "Here's the thing," "In practice," "What most teams miss"
- DON'T use: "Leverage," "Synergy," "Best-in-class," "Game-changing"
PRIMARY KEYWORD: "project management software for remote teams"
SECONDARY KEYWORDS: remote team collaboration tools, best PM software
for distributed teams, remote project tracking
STRUCTURE:
H1: How to Choose Project Management Software for a Remote Team
H2: Why Remote Teams Need Different PM Software
H2: 7 Features That Actually Matter (And 3 That Don't)
H3: Async communication tools
H3: Time zone visibility
H3: Workload balancing
H3: File sharing and documentation
H3: Mobile access
H3: Reporting and dashboards
H3: Integration with existing tools
H3: Features that sound good but don't matter (gamification,
built-in chat, AI summaries)
H2: How to Evaluate: A 3-Step Process
H2: Our Recommendation
H2: Common Mistakes to Avoid
SEO:
- Primary keyword in: title, H1, first 100 words, at least one H2
- Meta description: "Choosing PM software for a remote team? Here's
the 7 features that actually matter, 3 that don't, and a step-by-step
evaluation process."
- Internal links: link to /features/remote-teams and /case-studies/remote
REFERENCES:
- monday.com/blog/project-management/remote-teams — good structure
but too product-focused. We want more educational, less salesy.
- zapier.com/blog/best-project-management-software — good comparison
format but too listicle-style. We want more depth per point.
WHAT NOT TO DO:
- Don't just list tools with pricing. This is a "how to choose" guide.
- Don't assume the reader is technical. Explain integrations in plain terms.
- Don't mention our product until the recommendation section.
CTA: "Start a free trial" button at the end + inline CTA after the
evaluation section.
DELIVERY: Google Doc shared to editor@company.com by Friday COB.
Example 2: Email Newsletter Brief
CONTENT BRIEF — Weekly Newsletter Issue
SUBJECT: "The 3-minute pricing audit"
WORD COUNT: 400-600 words
FORMAT: Plain text in Google Doc (will be formatted in ConvertKit)
TARGET AUDIENCE:
- Freelancers and solopreneurs charging hourly or project rates
- Feeling underpriced but unsure how to raise rates
- Read the newsletter for quick, actionable business advice
TONE:
- Direct, punchy, slightly irreverent
- First person — write as the founder
- Short paragraphs (1-3 sentences max)
- Use line breaks liberally
STRUCTURE:
1. Hook (1-2 sentences that create curiosity)
2. The problem (why most freelancers underprice — 2-3 paragraphs)
3. The 3-minute audit (3 numbered steps the reader does right now)
4. Quick example showing before/after pricing
5. CTA: Reply with your current rate for personalized feedback
REFERENCES:
- Previous issue "Why $50/hour is killing your business" — match this
energy and pacing. Direct link in our archive.
WHAT NOT TO DO:
- Don't write a pricing guide. This is a quick audit, not a course.
- Don't use bullet points — this newsletter uses short paragraphs only.
- Don't end with "Hope this helps!" — end with a specific CTA.
Recovery & Fallbacks
- User doesn't have target keywords: Suggest 3 keywords based on the topic and let them pick. Include a note in the brief that keywords are tentative.
- User can't describe their brand voice: Ask for 3 pieces of existing content they like. Analyze and describe the voice for them.
- Writer delivers off-brief: The brief likely had a gap. Review which section was unclear and update the brief template for next time.
- User needs a brief template, not a one-off brief: Create a reusable template with placeholders that they can fill in for each new piece.
Constraints
- EVERY brief must include audience, tone, and structure — these three prevent 90% of revision cycles
- Include specific examples of good AND bad approaches
- Keep briefs under 2 pages — long briefs don't get read
- Include word count range, not a fixed number (e.g., 1,800-2,200, not 2,000)
- Always specify what NOT to do — writers need guardrails, not just goals
1---2name: content-brief3description: "Creates detailed content briefs for freelance writers with tone, structure, SEO targets, examples, and quality criteria. Use when a user is outsourcing content creation, needs to give clear direction to a writer, or wants to systematize their content production process."4metadata:5 source: https://skillmd.com/skills/reaperinvest/content-brief6---78# Content Brief Builder910## When to Use This Skill1112- Hiring a freelance writer and need to communicate expectations13- Outsourcing blog posts, articles, or web copy14- Building a content production system with multiple writers15- Getting inconsistent results from writers due to vague briefs16- Want to create a reusable brief template for recurring content1718## Core Principle1920**A GREAT BRIEF MAKES GREAT WRITING INEVITABLE. If you have to heavily edit the first draft, the brief failed — not the writer.**2122## Workflow2324### Step 1: Define the Content2526Ask the user:271. What type of content? (blog post, landing page, email, guide)282. What's the topic or working title?293. Who's the target reader?304. What's the primary keyword (for SEO)?315. What should the reader do after reading? (CTA)326. Any competing articles to beat or reference?3334**Minimum needed: questions 1, 2, and 3.**3536### Step 2: Build the Brief3738Include every section below:3940**1. Overview**41- Content type and working title42- Target word count43- Due date (if applicable)44- Target keyword + 3-5 secondary keywords4546**2. Audience**47- Who they are (role, experience level)48- What they already know about this topic49- What they need to learn or decide5051**3. Tone & Voice**52- Brand voice description (e.g., "expert but approachable, like explaining to a smart friend")53- Words to use / words to avoid54- Point of view (first person, second person, third person)5556**4. Structure**57- Required sections / outline58- H2 and H3 heading suggestions59- Specific elements to include (stats, quotes, examples, CTAs)6061**5. SEO Requirements**62- Primary keyword and target placement (title, H1, first 100 words, H2s)63- Secondary keywords to weave in naturally64- Internal links to include65- Meta description guidance6667**6. Examples & References**68- 2-3 links to articles that match the desired quality/style69- What's good about each reference (and what to do differently)7071**7. What NOT to Do**72- Common mistakes for this topic73- Off-topic tangents to avoid74- Competitor claims to not repeat7576**8. Delivery Format**77- File format (Google Doc, Markdown, Word)78- Image/visual requirements79- Header formatting expectations8081### Step 3: Deliver8283Format the brief as a clean, shareable document the user can hand directly to a writer.8485## Examples8687### Example 1: Blog Post Brief for a SaaS Company8889```90CONTENT BRIEF — Blog Post9192TITLE: How to Choose Project Management Software for a Remote Team93WORD COUNT: 1,800-2,200 words94FORMAT: Google Doc with H2/H3 headers9596TARGET AUDIENCE:97- Operations managers or founders at companies with 10-50 remote employees98- Currently using spreadsheets or basic tools (Trello, Asana free tier)99- Evaluating whether to upgrade to a paid PM tool100- Technical comfort: moderate (not developers, but not afraid of software)101102TONE:103- Expert but conversational — like a knowledgeable friend giving advice104- Second person ("you") throughout105- Confident but not salesy — we're educating, not pitching106- DO use: "Here's the thing," "In practice," "What most teams miss"107- DON'T use: "Leverage," "Synergy," "Best-in-class," "Game-changing"108109PRIMARY KEYWORD: "project management software for remote teams"110SECONDARY KEYWORDS: remote team collaboration tools, best PM software111for distributed teams, remote project tracking112113STRUCTURE:114H1: How to Choose Project Management Software for a Remote Team115H2: Why Remote Teams Need Different PM Software116H2: 7 Features That Actually Matter (And 3 That Don't)117 H3: Async communication tools118 H3: Time zone visibility119 H3: Workload balancing120 H3: File sharing and documentation121 H3: Mobile access122 H3: Reporting and dashboards123 H3: Integration with existing tools124 H3: Features that sound good but don't matter (gamification,125 built-in chat, AI summaries)126H2: How to Evaluate: A 3-Step Process127H2: Our Recommendation128H2: Common Mistakes to Avoid129130SEO:131- Primary keyword in: title, H1, first 100 words, at least one H2132- Meta description: "Choosing PM software for a remote team? Here's133 the 7 features that actually matter, 3 that don't, and a step-by-step134 evaluation process."135- Internal links: link to /features/remote-teams and /case-studies/remote136137REFERENCES:138- monday.com/blog/project-management/remote-teams — good structure139 but too product-focused. We want more educational, less salesy.140- zapier.com/blog/best-project-management-software — good comparison141 format but too listicle-style. We want more depth per point.142143WHAT NOT TO DO:144- Don't just list tools with pricing. This is a "how to choose" guide.145- Don't assume the reader is technical. Explain integrations in plain terms.146- Don't mention our product until the recommendation section.147148CTA: "Start a free trial" button at the end + inline CTA after the149evaluation section.150151DELIVERY: Google Doc shared to editor@company.com by Friday COB.152```153154### Example 2: Email Newsletter Brief155156```157CONTENT BRIEF — Weekly Newsletter Issue158159SUBJECT: "The 3-minute pricing audit"160WORD COUNT: 400-600 words161FORMAT: Plain text in Google Doc (will be formatted in ConvertKit)162163TARGET AUDIENCE:164- Freelancers and solopreneurs charging hourly or project rates165- Feeling underpriced but unsure how to raise rates166- Read the newsletter for quick, actionable business advice167168TONE:169- Direct, punchy, slightly irreverent170- First person — write as the founder171- Short paragraphs (1-3 sentences max)172- Use line breaks liberally173174STRUCTURE:1751. Hook (1-2 sentences that create curiosity)1762. The problem (why most freelancers underprice — 2-3 paragraphs)1773. The 3-minute audit (3 numbered steps the reader does right now)1784. Quick example showing before/after pricing1795. CTA: Reply with your current rate for personalized feedback180181REFERENCES:182- Previous issue "Why $50/hour is killing your business" — match this183 energy and pacing. Direct link in our archive.184185WHAT NOT TO DO:186- Don't write a pricing guide. This is a quick audit, not a course.187- Don't use bullet points — this newsletter uses short paragraphs only.188- Don't end with "Hope this helps!" — end with a specific CTA.189```190191## Recovery & Fallbacks192193- **User doesn't have target keywords:** Suggest 3 keywords based on the topic and let them pick. Include a note in the brief that keywords are tentative.194- **User can't describe their brand voice:** Ask for 3 pieces of existing content they like. Analyze and describe the voice for them.195- **Writer delivers off-brief:** The brief likely had a gap. Review which section was unclear and update the brief template for next time.196- **User needs a brief template, not a one-off brief:** Create a reusable template with placeholders that they can fill in for each new piece.197198## Constraints199200- **EVERY brief must include audience, tone, and structure** — these three prevent 90% of revision cycles201- Include specific examples of good AND bad approaches202- Keep briefs under 2 pages — long briefs don't get read203- Include word count range, not a fixed number (e.g., 1,800-2,200, not 2,000)204- Always specify what NOT to do — writers need guardrails, not just goals