Flagship Skill · Content brief authoring

The content brief authoring skill.

Thin briefs, thick briefs, and effective briefs are three different things.

A senior content strategist's playbook for authoring per-piece content briefs that actually guide writers (human or AI) to produce content worth publishing. The middle path between thin briefs (a keyword and a deadline; output reads generic) and thick briefs (a 4-page document nobody reads; output reads no better). The 12 fields that earn their keep, entity coverage for AEO and GEO, internal linking strategy, governance, and the discipline that keeps briefs under 2 pages.

Audience: content strategists, SEO content marketers, editorial leads, content ops managers, agencies running content programs at scale, plus any PM or marketer briefing a writer (human or AI).

View the skill on GitHubBrowse the full catalog

The keystone distinction

Three different shapes. Most teams produce one of the broken two.

The instinct to add more fields usually makes the brief worse. The instinct to be more specific in fewer fields usually makes the brief better. Most briefs that are not working are thin, not thick.

Too little

Thin brief

Keyword, word count, deadline. Maybe a one-line angle. The writer fills in everything else from priors. Output is generic, drifts off-topic, does not rank, does not convert. Cost is the rewrite cycle.

Too much

Thick brief

Four pages: executive summary, brand-guidelines refresher, comprehensive competitive analysis, voice guidelines, plus the actual brief. The writer skims for the outline, ignores the rest. Output reads no better. Cost is the authoring time.

The discipline

Effective brief

One to two pages. Twelve fields, every one earning its keep. Writer reads all of it because there is no fluff. Output is predictable enough that the editor does not have to rewrite the lede.

Every field has a job. If you can remove the field without degrading the output, remove it. The brief is the contract between editorial leader and writer; vague contracts produce vague output, overstuffed contracts produce output reflecting only what the writer read.

What is in the skill

Thirteen sections covered in the body.

The SKILL.md spans the per-piece brief discipline from the keystone framing through the 12 fields, the SERP intent and entity coverage that drive AEO and GEO, the writer handoff for both human and AI, and the governance that turns content production into a learning system.

  1. 01

    What this skill is for

    Composition with creative-brief, content-strategy, and content-and-copy. The clean reading order: strategy decides what to produce, this skill briefs each piece, content-and-copy writes it.

  2. 02

    Thin vs thick vs effective briefs

    The keystone distinction. Thin briefs produce generic output. Thick briefs produce output reflecting only what the writer skimmed. Effective briefs are 1 to 2 pages where every field earns its keep.

  3. 03

    The 12 fields of an effective brief

    Target keyword plus cluster, intent plus SERP format, audience plus JTBD, word count calibrated to SERP, heading structure, entity coverage, internal linking, external proof, anti-patterns, success criteria, voice reference, governance metadata. Plus the fields that do not earn their keep.

  4. 04

    Search intent classification

    Four standard intents (informational, navigational, commercial, transactional) plus the dominant SERP format check. The override pattern: when intent feels like X but the SERP shows Y, the SERP wins.

  5. 05

    Heading structure design

    H2 patterns (question-style, declarative, comparison, imperative). H3s only when they earn their keep. Featured snippet bait: 40 to 60 word answer paragraph immediately following an H2 question. Anti-patterns explicitly forbidden.

  6. 06

    Entity coverage for AEO and GEO

    Why AI engines cite entity-rich content. The discovery workflow: SERP top 10 entity scan, gap analysis, required-coverage list with placement notes. The placement plan, not just the entity list.

  7. 07

    Internal linking strategy

    Two link directions: outbound from this piece (3 to 5 specified), inbound to this piece post-publish (1 to 3 queued). Orphan-content prevention. Self-cannibalization check before briefing.

  8. 08

    Brief templates by content type

    Pillar, supporting, comparison, listicle, how-to, thought leadership. The 12 fields stay constant; the weight of each field shifts by content type. Worked examples for each.

  9. 09

    The brief-to-writer handoff

    Five-step shape regardless of human or AI writer: brief delivered, clarifying questions, success-criteria acknowledgment, first draft with reference note, editor review against brief. Structured input pattern for AI agents.

  10. 10

    Brief governance

    Versioning with bump triggers. Single approver who is also the editor. Archival alongside the published piece. Audit trail that turns content production into a learning system.

  11. 11

    Common failure modes

    Ten-plus patterns: too thin, too thick, ignored brief, wrong target keyword, mismatched SERP intent, no internal links, generic output, comprehensive brief that still fails to rank, no post-publish evaluation, writer drift across the same brief.

  12. 12

    The framework: 12 considerations

    Target keyword plus cluster, intent plus format, audience plus JTBD, SERP-calibrated word count, heading structure, entity coverage, internal linking, external proof, anti-patterns, success criteria, versioning plus approver, brief stays under 2 pages.

  13. 13

    The brief is the contract

    Vague contracts produce vague output. Overstuffed contracts produce output reflecting only what the writer read. The discipline is writing contracts the writer can absorb in 5 minutes and execute against in the next 5 hours.

The 12 fields

What an effective brief contains.

The 12 fields apply across content types. Pillar pieces, supporting cluster pieces, comparisons, listicles, how-to guides, thought leadership: same fields, different weights per type.

  1. 01Target keyword + supporting cluster
  2. 02Search intent + dominant SERP format
  3. 03Target audience + JTBD
  4. 04Word count calibrated to SERP
  5. 05Heading structure outline
  6. 06Required entities, statistics, citations
  7. 07Internal linking strategy
  8. 08External proof points
  9. 09Anti-patterns
  10. 10Success criteria
  11. 11Author voice and tone reference
  12. 12Brief versioning + approval

The 13th field is what does NOT belong in the brief: executive summary, brand-guidelines refresher, comprehensive competitive landscape, brand history. Link to those; do not repeat them. Each removed field shortens the brief and makes the rest more legible.

Reference files

Eight references that go alongside the SKILL.md.

The references hold the per-content-type templates, the SERP intent classification framework, the heading structure patterns, the entity coverage checklist for AEO and GEO, the internal linking strategy, the writer handoff protocols for human and AI, the governance patterns, and the failure-mode catalog.

  • references/brief-templates.md

    Six templates: pillar, supporting cluster, comparison, listicle, how-to, thought leadership. Each template names which of the 12 fields lean heavier and which lean lighter for that content type. Worked examples per template.

  • references/search-intent-classification.md

    Four-intent framework. Dominant SERP format check (article, listicle, comparison, video, tool, hybrid). The override pattern when intent and format mismatch. AEO and GEO citation considerations.

  • references/heading-structure-patterns.md

    H2 patterns (question, declarative, comparison, imperative). H3 inclusion criteria. Featured snippet bait pattern with example. H2 ordering rules. Anti-patterns the brief should explicitly forbid.

  • references/entity-coverage-checklist.md

    Why entity coverage matters for AEO and GEO. The five-step discovery workflow from SERP top 10. Citation drivers beyond entities: specific statistics, named experts, direct definitions, comparison tables. The placement-plan pattern.

  • references/internal-linking-strategy.md

    Outbound link selection with anchor text and target page. Inbound link queue as post-publish task. The orphan-content failure mode and the 5-link rule diagnostic. The self-cannibalization check before briefing.

  • references/writer-handoff-protocols.md

    Five-step handoff regardless of writer type. Human-writer handoff: brief delivery, clarifying questions, acknowledgment, draft with reference, editor review. AI-agent handoff: structured YAML or JSON input, ambiguity surfacing, success-criteria anchoring.

  • references/brief-governance-patterns.md

    Versioning with bump triggers (target keyword change, audience shift, scope expansion, success-criteria change). Single approver who is also the editor. Archival patterns (Notion, dbt, CMS metadata, git repo). The audit trail that compounds across pieces.

  • references/common-brief-failures.md

    Ten-plus failure patterns with diagnoses and fixes. Cross-references to other reference files. The pattern across most failures: thin briefs, not thick ones; the instinct to add fields usually makes briefs worse.

Browse all reference files on GitHub

Pairs with these platforms

Four content and SEO platforms for brief generation and publishing.

The skill is the brief discipline; the integration pages are the platform-specific tactics. Frase ships a read-write MCP across the SEO + GEO content lifecycle, brief generation included. AirOps wraps the brief pipeline in a managed workflow surface. Webflow and Contentful are publishing destinations where briefed content lands; their MCPs cover CMS-aware writes.

Notion is intentionally not cross-linked here. Its existing microsite under the workflow category covers creative-direction briefs (the project-brief sibling) specifically; pairing it here would muddle the per-piece editorial brief focus of this skill. The Notion MCP still runs CMS-style briefs queryable as database rows for teams that want that pattern.

Bridges to sister skills

Three sister skills compose into the content discipline.

This skill does not stand alone. The clean reading order is: content-strategy decides what to produce (program scope), this skill briefs each piece (per-piece scope), content-and-copy writes it (execution scope). creative-brief is the fourth in the family but covers a different artifact: project briefs at project scope. Same word, different shape.

  • Program companion (above)

    content-strategy

    Program-level editorial strategy: pillars, calendar, topic clusters, governance, topical authority. Decides what to produce across a quarter or year. This skill briefs each piece content-strategy decides to ship.

  • Writing companion (below)

    content-and-copy

    The writing itself: voice, structure, edit pass, tone calibration. Execution scope for general editorial. The piece this skill briefs is the piece content-and-copy writes.

  • Sibling, distinct purpose

    creative-brief

    Project brief for design, dev, or agent kickoff at project scope: a new website, app, brand, or campaign. Same word ('brief') different artifact. Use creative-brief to scope a project; use this skill to brief a piece inside an ongoing content program.

Where this skill fits in the content suite

The first of five in the content suite.

Content brief authoring is the first skill in a planned five-skill content suite. The brief is the input to everything else; the suite anchors here for that reason. Subsequent skills cover pillar content architecture (multi-piece programs), programmatic SEO (templated content at scale), editorial QA (review and publish discipline), and AI content collaboration (running an editorial team where some writers are agents).

Each skill in the suite assumes the brief discipline from this skill and extends it. Pillar content architecture briefs cluster pieces in coordination, not one-off; programmatic SEO briefs templates that generate hundreds of pieces from one brief; editorial QA reviews drafts against the brief, not against personal taste; AI content collaboration runs the brief-to-writer handoff at the team level when some writers are agents.

The suite ships sequentially. Subsequent skills do not exist yet; cross-linking lands when the skill pages ship. For now, the brief discipline anchors the program and the four content and SEO platforms above cover the platform-specific tactics underneath.

Open source under MIT

Read the SKILL.md on GitHub.

The skill source lives in the rampstackco/claude-skills repository alongside dozens of other skills covering the full lifecycle of brand and product work. MIT licensed.

View SKILL.mdBrowse the full catalog

Frequently asked questions.

What is a content brief, and why does it need its own skill?
A content brief is the per-piece contract between editorial leader and writer. It defines what the piece is, who it is for, what it has to cover, and what good looks like. The skill exists because most briefs are either too thin (a keyword and a deadline; the writer fills in everything else from priors and produces generic output) or too thick (a 4-page document nobody reads; the writer skims for the headline). The middle path takes discipline that does not transfer automatically from writing or editing experience.
How is this different from creative-brief, content-strategy, and content-and-copy?
creative-brief is a project brief: a new website, app, brand, or campaign at project scope. content-strategy is a program-level editorial strategy: pillars, calendar, governance across a quarter or year. content-and-copy is the writing itself: voice, structure, edits. This skill is the per-piece editorial brief between strategy (program) and writing (execution). The clean reading order: content-strategy decides what to produce, this skill briefs each piece, content-and-copy writes it.
What are the 12 fields the brief should cover?
Target keyword plus supporting cluster, search intent classification with dominant SERP format, target audience and JTBD, word count calibrated to SERP, heading structure outline, required entities and citations, internal linking strategy (outbound and inbound), external proof points, anti-patterns, success criteria, voice and tone reference, and the brief versioning plus approver. Each field has a job. If a field can be removed without changing writer behavior, it should be removed.
How does the brief support AI writers (Claude, Frase, AirOps)?
The 12 fields apply to AI writers identically; the medium is structured. The brief becomes a YAML or JSON object the agent ingests. Frase, AirOps, and similar tools structure briefs in their own schemas; the same 12 fields appear regardless. The agent's first response should surface ambiguities in the brief; the editor reviews the agent's draft against the brief, not against personal taste. Same contract, different writer.
What is the role of entity coverage for AEO and GEO?
AI engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Mode) tend to cite content that mentions the entities the SERP top-ranking pages mention. Entity coverage is the citation signal alongside specific statistics with sources, named experts, direct definitions, and comparison tables. The brief lists required entities (mentioned by 7+ of 10 SERP pages), standard entities (3 to 6 pages), and gap entities (1 to 2 pages, treated as differentiation opportunity). Without entity coverage in the brief, the writer's piece passes a string-match check but does not actually demonstrate topical depth.
Why is the brief approver also the editor?
Splitting the roles is how briefs and reviews drift apart. If a strategist briefs the piece and a different person edits it, the editor changes the lede because of personal taste, not because of the brief. Single approver and single editor on the same person enforces taste consistency: the brief is the contract, and the same person holds both sides of the contract. The exception is high-stakes pieces (pillar content, thought leadership with named author) where a second reader provides input but does not approve. The single approver still decides.