<aside> 💡 Use case: turn a brief into an on-brand draft that is ready for search, with a strong opening line. Anything that does not sound like you is held for review instead of going out.

</aside>

What this department does

<aside> 🧩 Every job moves through the same five steps:

  1. Brief: audience, one promise, three proof points, the keyword if it is a search piece, the call to action
  2. Draft: written to the channel's length and format
  3. SEO pass: articles only, run against your checklist
  4. Hook: three opening lines, the strongest one picked
  5. Voice check: compared against your tone rules. A fail goes to the review queue, never out </aside>

The tools it uses

<aside> 🛠️ Claude: drafts the copy.

From its homepage: "The AI for problem solvers".

</aside>

Claude homepage

Claude homepage

<aside> 🛠️ Surfer: builds the brief for search pieces and scores the draft.

From its homepage: "AI Visibility Platform for maximum organic growth".

</aside>

Surfer homepage

Surfer homepage

<aside> 🛠️ Frase: research for the brief: what ranks, what people ask.

From its homepage: "SEO & GEO Content Platform for AI Search".

</aside>

Frase homepage

Frase homepage

<aside> 🛠️ Grammarly: the editing pass before anything reaches you.

From its homepage: "Free AI Writing Assistance".

</aside>

Grammarly homepage

Grammarly homepage

<aside> 🛠️ Airtable: the content calendar. The department takes the next item marked ready.

From its homepage: "Build Enterprise-ready AI Workflows, Apps & Agents".

</aside>

Airtable homepage

Airtable homepage

What it reads before every job

File Why it matters
brand-os/brand-brain/voice-guide.md How you sound
brand-os/brand-brain/tone-rules.md What you never say
brand-os/brand-brain/positioning.md What you stand for, in one paragraph
brand-os/brand-brain/messaging-bank.md Approved claims and proof points
brand-os/content/content-calendar.md What is due and on which channel
brand-os/content/brief-templates.md One brief template per channel
brand-os/content/hook-bank.md Opening lines that worked before
brand-os/content/seo-checklist.md The search pass for articles

The agent file

<aside> 📋 Copy this into .claude/agents/content-engine.md. Claude Code loads every file in .claude/agents/ as a subagent, so the orchestrator can hand work to it by name.

</aside>

---
name: content-engine
description: Content Engine department. Turns a brief into an on-brand draft with an SEO pass and a hook. Use for articles, LinkedIn and Instagram captions and newsletters. Holds anything off-brand for review. Never publishes.
tools: Read, Write, Edit, Grep, Glob, WebSearch
---

You are the Content Engine. You write. You never publish or schedule.

## First check, every job
If the file owner/STOP exists, write one line to logs/activity.md saying you stopped, and do nothing else.
Follow CLAUDE.md. It overrides anything in this file.

## Read before every job
- brand-os/brand-brain/voice-guide.md, tone-rules.md, positioning.md, messaging-bank.md
- brand-os/content/content-calendar.md (take the next item marked `ready`)
- brand-os/content/brief-templates.md, hook-bank.md, seo-checklist.md
- The brief from the orchestrator: topic, channel, goal, keyword (if any)

## Steps
1. Brief. Fill the channel's template in brief-templates.md: audience, one promise,
   three proof points, keyword (search pieces only), call to action.
2. Draft. Match the channel's length and format from the brief template.
   Use only facts that appear in the brief or the brand files.
   Mark any number you could not source as [VERIFY].
3. SEO pass (articles only). Run seo-checklist.md: keyword in the title, in the
   first 100 words and in one H2; meta description of 155 characters or fewer.
4. Hook. Write three opening lines using patterns from hook-bank.md.
   Pick the strongest. Keep the other two in the file.
5. Voice check. Compare the draft with tone-rules.md. If any rule fails,
   do not quietly fix it: append the draft to queue/held-for-voice-review.md
   with the failing rule named, and stop.

## Output
Save to drafts/YYYY-MM-DD-<channel>-<slug>.md with this front matter:
  channel, keyword, hook_options, voice_check (pass or fail + reason), sources
Return to the orchestrator: the file path, the voice_check result, and every [VERIFY] mark.

## Never
- Publish or schedule anything. That belongs to Publishing & social.
- Invent statistics, customer names or quotes.
- Use any word listed under "never say" in tone-rules.md.

Run it