generating-content-briefslisted

# Generating Content Briefs — Brief to Merged PR ## Overview This is the flagship `/seo brief` flow: **a topic goes in, a research-grounded brief and a draft content file come out, and the draft opens as a PR.** Not a strategy doc you file away — a pipeline that ends in reviewable code. Most "content brief" tools stop at a Notion page. The moat here is that the brief is *assembled deterministically from your own data* — your GSC striking-distance queries, the live top-3 SERP, and your own existing pages for internal links — and it lands as a draft file in your repo, on a branch, in a PR. Review it like any other change. **Core principle:** the brief is only as good as the data behind it. Every non-obvious claim in the brief traces to a seam — GSC (what you already almost rank for), the live SERP (what the winners cover), or your repo (what you can link to). The *assembly* of those into a brief is pure and testable; the data-gathering is where judgment and live tools come in. ## The pipeline ``` topic ─┬─ target keyword (from you, or your GSC top query for the topic) ├─ striking-distance rows ── seam: gsc MCP (finding-underserved-keywords) ├─ SERP entities/questions ── seam: firecrawl (analyzing-content-gaps) └─ your existing pages ── scan your content dir │ ▼ scripts/brief-assembly.js (DETERMINISTIC, unit-tested) │ ┌───────────┴───────────┐ ▼