A senior content strategist's playbook for authoring per-piece content briefs that actually guide writers to produce content worth publishing.

Most content briefs are some flavor of broken. The thin version is a keyword, a word count, and a deadline; the writer fills in everything else from scratch and the output is generic. The thick version is a 4-page document nobody reads, that the writer skims for the headline and the outline and ignores the rest. Either way, the brief failed at its job: making the writer's work easier and the output more predictable.

This skill is the middle path. It defines the 12 fields that earn their keep in a content brief, the fields that bloat without helping, and the discipline of writing briefs that route a writer (human or AI) toward a content piece that ranks for its target keyword, gets cited by AI engines, converts the right reader, or whatever the success criteria say. It assumes you have decided what to write (see for program-level decisions) and now you are briefing each piece. The piece itself gets written separately (see ).

When to use this skill: briefing a writer (human or AI) on an individual content piece, auditing existing briefs that are not producing good content, building a brief template for a content program, or running a brief-generation pipeline through Frase, AirOps, or another tool.

This skill spans the per-piece editorial brief discipline. It composes with three sister skills, and the distinction between them is what keeps each one sharp.

The clean reading order: decides what to produce; this skill briefs each piece; writes it. If the team is briefing a redesign or a new brand build, that is , not this skill.

The audience: content strategists, SEO content marketers, editorial leads, content ops managers, agencies running content programs at scale, and any PM or marketer briefing a writer (human or AI). The voice is senior content strategist to junior content marketer. Specific, opinionated, honest about what makes a brief useful versus useless.

The keystone distinction. Three concrete shapes.

Thin brief. Keyword, word count target, deadline. Maybe a one-line summary of the angle. The writer fills in everything else from scratch. Output is generic, drifts off-topic, does not rank, and does not convert. The cost is the rewrite cycle: editor spends two hours rewriting because the writer chose the wrong intent, the wrong audience, or the wrong outline.

Thick brief. A 4-page document with executive summary, brand-guidelines refresher, comprehensive competitive analysis, voice guidelines, plus the actual brief somewhere in the middle. The writer skims for the outline, ignores the rest. Output is not materially better than from a thin brief because the writer never read most of the document. The cost is the authoring time: the strategist spends three hours producing pages of context the writer will never absorb.

Effective brief. One to two pages. Every field earns 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. The cost is the discipline of cutting fields that do not change writer behavior.

The discipline. Every field in the brief 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 that reflects only the parts the writer read.

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

A useful brief has 12 fields. Skip any of them and the writer fills the gap from priors; the gap is where output drifts.

The fields that do not earn their keep, and should be omitted from briefs unless the writer is brand new to the program:

Detail and templates per content type in

references/brief-templates.md

.

The four standard intents:

The dominant SERP format check. After classifying intent, scan the SERP top 10 and tag the dominant format: article, listicle, comparison, video, tool, hybrid. The dominant format tells you the shape of the piece, which is more decisive than the intent label.

The override pattern. When the intent feels informational but the SERP shows mostly listicles, write the listicle. When the intent feels commercial but the SERP shows mostly long-form articles, write the article. The SERP is the source of truth, not your priors. Rankings come from matching the SERP's accepted shape; deviating costs ranking.

The AEO/GEO consideration. AI engines tend to favor pieces that match SERP intent format because the intent classification was trained on the SERP corpus. Mismatched format is a citation risk in addition to a ranking risk.

Detail in

references/search-intent-classification.md

.

Heading hierarchy patterns the brief should specify:

Anti-patterns the brief should explicitly forbid:

Detail in

references/heading-structure-patterns.md

.

AI engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Mode) tend to cite content that mentions the entities the SERP top-ranking pages mention, includes specific statistics with sources, contains citation-formatted proof points, and demonstrates topical depth via entity coverage.

The entity discovery pattern, run before briefing the piece:

The brief lists the entities the writer must mention, with light context on why each matters. The writer is not expected to research each entity from scratch; the brief includes a one-line note ("CUPED is the variance-reduction technique used by data-warehouse-experimentation teams; mention in the methodology section") so the writer can integrate without breaking flow.

Tools that automate this: Frase has entity-gap analysis built in; AirOps composes the same analysis through its workflow builder; Surfer SEO ships entity coverage scoring. The skill is tool-agnostic; the workflow is what matters.

Detail in

references/entity-coverage-checklist.md

.

The brief should specify two link directions:

The orphan-content failure mode: piece publishes, no other piece links to it, search engines deprioritize it, AI engines do not see it as cluster-anchored. Prevented by upstream-link planning in the brief.

The self-cannibalization check: if this piece would compete with an existing piece for the same keyword cluster, the brief flags it explicitly. The options are consolidate (merge into the existing piece), differentiate (the brief sharpens the angle so the two do not compete), or kill one. Flagging late, after the piece is written, costs more than flagging in the brief.

Detail in

references/internal-linking-strategy.md

.

Different content types call for different brief shapes. The 12 fields are constant; the weight of each field shifts.

Each template gets a worked example in

references/brief-templates.md

.

Whether the writer is human or AI, the handoff has the same shape.

For AI handoff specifically, the brief becomes a structured prompt or a tool input. Frase, AirOps, and similar tools structure briefs as YAML or JSON for machine consumption; the same 12 fields apply. The structured format is the only difference; the contract is the same.

Detail in

references/writer-handoff-protocols.md

.

Versioning. Every brief has a version. Significant changes (target keyword change, audience shift, scope expansion) bump the version; cosmetic edits do not. The writer always works from the current version, not a stale draft pasted into Slack three weeks ago.

Approval. The brief approver is the editorial owner of the content program. Single approver, not a committee. The approver is also the editor on the back end, so the same person is responsible for both the contract and the review. Splitting these roles is how briefs and reviews drift apart.

Archival. After publish, the brief is archived alongside the content piece (Notion database row, dbt model, content management system metadata, whatever the team's source of truth is). Future content audits reference both brief and published piece to assess gap between intent and execution. Without the brief in the archive, a content audit cannot tell whether the piece succeeded against the original goal or drifted from it.

Detail in

references/brief-governance-patterns.md

.

Rapid-fire. Diagnoses and fixes in

references/common-brief-failures.md

.

When authoring or auditing a content brief, walk these 12 considerations.

The output of the framework is a brief document the writer can absorb in 5 minutes and execute against in the next 5 hours.

A content brief is the contract between editorial leader and writer. If the contract is vague, the output is vague. If the contract is overstuffed, the output reflects only the parts the writer read. The discipline is writing contracts the writer can absorb in 5 minutes and execute against in the next 5 hours; that is the entire job.

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

When in doubt about whether a brief is ready, ask: are all 12 fields populated, do they each earn their keep, is the SERP intent matched, are the entities listed, are the internal links specified, is the success criteria measurable, and is the document under 2 pages? If yes to all of those, ship the brief and let the writer work.