# Usage: curl -sSL https://seed.show/marketing.content.pipeline | bash -s <install-path>
# <install-path> is the directory where the file should land.

set -euo pipefail
[ -z "${1:-}" ] && {
  echo "install requires a path: curl -sSL https://seed.show/marketing.content.pipeline | bash -s <install-path>" >&2
  exit 1
}
TARGET="$1"
mkdir -p "$TARGET"
DEST="$TARGET/seed-fold.a0gCRg.folded.md"

cat > "$DEST" <<'PORTDOWN_8A5A77DB'
<!--
This is a `.folded.md` archive — a directory packed into one markdown
file. The markers below are load-bearing; don't edit them directly.

To unpack (requires bash — if you have no shell, tell the user):
  1. curl -sSLf https://fold.dom.vin/skill | bash -s <INSTALL_DIR>
  2. <INSTALL_DIR>/fold/scripts/unfold <this-file>
     (or: unfold <this-file>  if fold/scripts is on your PATH)
-->

---
fold: true
marker: ff37bc
at: 2026-05-07T16:16:17Z
root: seed-pack.XuiZ5q
---

<!--fold:ff37bc@file path="README.md" mode="644"-->
# marketing.content.pipeline

Content operations context for agents. Level: practitioner — not introductory. What to know before touching a brief, running a content workflow, or advising on editorial process.

**Do not hallucinate:** specific platform features, tool capabilities, org structures at named companies, or performance benchmarks. Fetch sources.md for current methodology references.

## Mental model: content pipeline as manufacturing

Content operations is a manufacturing system with distinct stages, defined handoffs, and measurable throughput. The analogy is not poetic — it is operational. Like manufacturing, bottlenecks compound upstream: a defect introduced at brief costs 10× more to fix at distribution than at brief time. Rework is the primary inefficiency. The goal is zero rework through gate discipline, not speed through any single stage.

Three properties define a functioning content operation:

**Throughput integrity.** The system can predict how much content it will produce in a given period, with what resources, at what cost. Not "we publish when we can" but "we have a 6-week production runway, 4 briefed pieces per week, and can absorb 2 emergency requests without slipping the queue." Without throughput visibility, editorial teams are always reactive.

**Quality consistency.** Content meets the same standard regardless of who wrote it, which agency produced it, or how close the deadline was. This requires documented standards — voice, accuracy, fact-check requirements, legal review thresholds — that are not locked in any individual's head. One senior editor's taste is not a quality system.

**Distribution integration.** Production and distribution are not sequential. Distribution requirements shape production decisions. SEO metadata, channel-specific formatting, social variants, email preview text: these are part of the content, not afterthoughts added at publish time. A pipeline that treats distribution as a post-production step will produce content that underperforms in every channel.

## The brief as the load-bearing artifact

The content brief is the most important document in the pipeline. Everything downstream — research, draft, review, optimization — depends on the quality of the brief. A weak brief produces a weak draft. A missing brief produces a rework cycle.

A complete brief answers:

- **Why this piece?** The business objective it serves, the funnel stage it targets, and the metric that will tell you it worked.
- **Who reads it?** A specific reader persona at a specific moment of decision — not "B2B marketers" but "a demand gen manager at a 200-person SaaS company who has been tasked with justifying headcount and needs to show pipeline attribution."
- **What should the reader believe or do after reading?** One specific belief change or action. Not "learn about our capabilities" — that is not a job.
- **What does the reader already believe?** The assumption the piece has to overcome, or the knowledge gap it fills. This shapes angle and tone more than any style guide.
- **What are the constraints?** Word count range, format (listicle, narrative, comparison), required SME sources, legal review trigger, publish window, distribution channels and their specific requirements.

A brief without a specific reader and a specific belief change is a content request form, not a brief.

## What agents get wrong

**Writing before briefing.** The instinct to produce a draft immediately — given a topic, a headline, sometimes just a keyword — skips the only step that makes the draft useful. Content without a brief is content optimized for nothing. It will be revised until it has a brief, retroactively, by the editor. Brief first, always.

**Treating all content types as equivalent workflow.** A thought-leadership essay, a product comparison page, a customer story, an email nurture sequence, and a technical how-to guide have different briefs, different review requirements, different SEO profiles, and different distribution paths. Applying the same production workflow to all of them optimizes for the wrong things at every stage. Content type determines process, not the other way around.

**Ignoring distribution in the production process.** SEO requirements need to be decided at brief time. Social variants require a different editorial voice than the long-form original — they cannot be cut-and-pasted from the intro paragraph. Email subject lines require A/B framing that only makes sense if email was a named distribution channel at brief time. Production that ignores distribution produces content that has to be reworked for every channel.

**Skipping review to hit deadlines.** The review stages most often compressed under deadline pressure — SME accuracy, legal, brand — are not optional quality gates. They are risk management. A published piece with a factual error, an unlicensed claim, or an off-brand voice costs more than a missed publish date. The pipeline should have buffer for review, not a culture of skipping it.

**Not defining "done."** Done is not "draft approved." Done is: published, distributed across all named channels with correct UTMs, indexed, and measured against the metric named in the brief at 30 days. Without a definition of done, work accumulates in a perpetual finishing state and the pipeline loses throughput visibility.

## What AI is changing

**What AI handles well in the pipeline:**
- Brief generation from strategy inputs — AI can scaffold a brief from audience, keyword, and objective inputs faster than a human starting from scratch, but the brief still requires editorial judgment to validate the angle and belief-change statement
- First-draft assistance for formats with well-defined structure (comparison pages, listicles, how-to guides) — AI reduces time-to-draft, not time-to-brief
- SEO optimization passes — title tag variants, meta description testing, heading structure review against keyword hierarchy
- Translation and localization at volume — AI handles linguistic adaptation; human editorial review handles cultural accuracy and brand voice
- Repurposing existing content — AI can extract social variants, email summaries, and script outlines from long-form originals, but the distribution-specific voice still requires human review

**What stays human:**
- Brand voice judgment — AI can approximate a style guide; it cannot judge whether a piece is on-brand in the way a senior editor can
- Original insight and point of view — AI recombines existing information; original research, proprietary data, and contrarian angles require human authorship to be credible
- Audience relationship and editorial trust — readers who trust a publication trust the humans behind it; AI-generated content disclosed or perceived undermines that trust at the publication level, not just the piece level
- Editorial standards enforcement — which claims require legal review, which sources are credible, when a piece's angle is irresponsible — these are judgment calls, not rule lookups

**Measuring AI-assisted content quality:**
- Track AI-assisted vs. human-authored pieces separately in performance analytics — if AI-assisted pieces underperform on engagement and conversion metrics, the pipeline is using AI in the wrong stages
- Fact-check failure rate is the leading indicator of brief and research quality, not draft quality — AI drafts that fail SME review signal weak briefs, not bad AI
- Revision cycles are the operational cost metric: AI that reduces revision cycles is adding value; AI that increases them (by producing plausible-sounding drafts that require full rewrite) is not
<!--fold:ff37bc@file path="sources.md" mode="644"-->
# sources

Fetch these at task time. Ordered by relevance. These are methodology and framework references — fetch for structural guidance, not platform-specific feature documentation.

## Content operations and editorial workflow

1. Content Marketing Institute — content operations frameworks, workflow guides, editorial process:
   https://contentmarketinginstitute.com/articles/content-operations/

2. Content Marketing Institute — content governance, brand standards, review processes:
   https://contentmarketinginstitute.com/articles/content-governance/

3. Ann Handley's Everybody Writes — quality standards, voice standards, what makes content earn attention:
   https://annhandley.com/everybodywrites/

4. Convince & Convert — content operations maturity model, stages from ad hoc to systematic:
   https://www.convinceandconvert.com/content-marketing/content-operations/

## Content strategy and briefing

5. Contently — content strategy resources, brief frameworks, content audits, measurement:
   https://contently.com/strategist/

6. Ahrefs — content brief methodology, keyword research integration, SEO requirements in briefing:
   https://ahrefs.com/blog/content-brief/

7. Semrush — content marketing workflow, SEO audit, brief, production, distribution cycle:
   https://www.semrush.com/blog/content-marketing-workflow/

## Distribution and measurement

8. Content Marketing Institute — editorial calendar templates, distribution planning:
   https://contentmarketinginstitute.com/articles/editorial-calendar-templates/

9. Animalz — content measurement frameworks, what to track and why:
   https://www.animalz.co/blog/content-marketing-metrics/

10. First Page Sage — content ROI measurement, pipeline attribution, content-to-revenue models:
    https://firstpagesage.com/reports/

## AI in content production

11. Content Marketing Institute — AI in content marketing, workflow integration, risks:
    https://contentmarketinginstitute.com/articles/ai-content-marketing/

12. Animalz — AI writing quality standards, where AI helps and where it hurts:
    https://www.animalz.co/blog/ai-content/
<!--fold:ff37bc@file path="workflow.md" mode="644"-->
# Content production stage-gate framework

The pipeline moves through eight stages. Each has a gate — a set of questions that must be answered before the work advances. Moving forward without clearing a gate pushes the unresolved decision downstream where it costs more to fix. Bottlenecks compound upstream: a defect introduced at brief is cheapest to fix at brief, expensive to fix at review, and most expensive to fix post-publish.

---

## Stage 1: Strategy brief

**What it is:** The upstream document that justifies the content program. Defines the audience, the business objectives, the content themes, and the success metrics. Usually quarterly or annual.

**Gate questions before moving to content brief:**
- What business objective does this content program serve, and how will we measure it? (Not "brand awareness" — a metric.)
- Who is the specific reader? Persona with job title, company size, current belief, current problem.
- What themes will this quarter's content address, and why those themes for this audience now?
- What is the production capacity? How many pieces, what formats, what channel mix?
- Who owns the editorial calendar and has authority to prioritize and deprioritize?

**Who must sign off:** Head of content or CMO.

---

## Stage 2: Content brief

**What it is:** The brief for a single piece. The load-bearing artifact. Derived from the strategy brief but specific to this piece.

**Gate questions before moving to research/outline:**
- What is the specific reader persona and their moment of decision?
- What is the one belief change or action this piece produces?
- What does the reader already believe that this piece must address or overcome?
- What is the format, word count range, and publish target date?
- Which review stages apply? (SME accuracy / legal / brand — and who specifically?)
- What are the SEO requirements? (Target keyword, secondary keywords, title tag, meta description, internal link targets.)
- What are the distribution channels and their specific requirements? (Social variants needed? Email version? Syndication?)

**Who must sign off:** Assigning editor or content lead.

---

## Stage 3: Research and outline

**What it is:** Source gathering, SME interviews if required, and a structured outline reviewed before drafting begins.

**Gate questions before moving to draft:**
- Are all factual claims in the outline sourced? (No draft should introduce a claim that hasn't been verified at outline.)
- Has the SME or subject matter reviewer seen the outline if accuracy is a concern?
- Does the outline serve the brief's stated belief change — or did it drift into a different angle during research?
- Are SEO heading structure requirements reflected in the outline?

**Who must sign off:** Assigning editor.

---

## Stage 4: Draft

**What it is:** The written piece, produced to brief.

**Gate questions before moving to review:**
- Does the draft match the brief's stated format, word count, and angle?
- Does it produce the belief change or action named in the brief?
- Is the voice consistent with brand standards?
- Are all factual claims cited or clearly attributed?
- Is the SEO structure implemented? (Heading hierarchy, keyword placement, meta content drafted.)
- Are distribution variants drafted (social, email) or flagged for production?

**Who must sign off:** Writer / content producer (self-review before submitting for editorial).

---

## Stage 5: Review (SME / legal / brand)

**What it is:** Parallel or sequential review by subject matter experts, legal (if applicable), and brand. The review stage most often compressed under deadline pressure; the stage where compressing is most costly.

**Gate questions before moving to SEO optimization:**
- SME review: Are all technical or factual claims accurate? Have claims been verified by a qualified reviewer, not just a generalist?
- Legal review: Does this piece make claims that trigger a legal review requirement? (Performance claims, competitor comparisons, regulated industry content.) If so, has legal cleared it?
- Brand review: Is voice, tone, visual language, and messaging consistent with current brand standards?
- Have all review comments been resolved — not just acknowledged?

**Who must sign off:** Each applicable reviewer. Unresolved legal comments are a hard stop.

---

## Stage 6: SEO optimization

**What it is:** Final optimization pass for search — title tag, meta description, heading structure, internal linking, image alt text, schema if applicable.

**Gate questions before moving to publish:**
- Is the title tag within character limits and does it include the target keyword?
- Is the meta description accurate to the content and written to drive clicks?
- Is the heading structure correct (H1 → H2 → H3) and does it reflect the keyword hierarchy from the brief?
- Are internal links implemented to the target pages named in the brief?
- Has the piece been checked against current search intent for the target keyword? (Did the brief's angle match what searchers actually want?)

**Who must sign off:** SEO lead or content lead with SEO responsibility.

---

## Stage 7: Publish

**What it is:** Pushing the content live on the appropriate platform(s).

**Gate questions before moving to distribution:**
- Is the CMS entry complete? (Tags, categories, author, publish date, featured image with alt text, canonical URL if syndicated.)
- Have all technical elements been verified? (Links work, images load, formatting is correct on mobile.)
- Is the piece indexed or set to index? (Intentional noindex is a deliberate decision, not an oversight.)
- Is the UTM structure in place for distribution links?

**Who must sign off:** Content operations or publishing lead.

---

## Stage 8: Distribution and measurement

**What it is:** Active distribution across channels and measurement against the metrics named in the strategy brief. This stage is ongoing — not a single handoff — and is the stage most often treated as complete when it has only just started.

**Distribution gate (at publish):**
- Have all distribution variants been published — social, email, syndication, paid amplification — with the correct UTMs? (UTMs without channel/campaign/content parameters are not UTMs; they are decoration.)
- Is the piece tagged in analytics to attribute performance to the correct campaign and content theme? Can the analytics report show this piece's contribution to pipeline, conversion, or the metric named in the brief?
- Have paid amplification parameters (audience targeting, budget, duration) been set if this piece has a paid distribution component?
- Is the canonical URL set correctly if the piece is syndicated? Syndication without canonical is an indexing risk, not a distribution win.

**Measurement at 30 days:**
- Is organic traffic on track against the projection in the brief? If traffic is below projection, the first diagnostic is search intent alignment — did the brief's angle match what searchers actually want for the target keyword? Check by reviewing the SERP for the target keyword against the piece's angle.
- Is engagement (time on page, scroll depth, clicks to next step) above the content type's baseline? Low engagement with high traffic signals a mismatch between the headline's promise and the content's delivery — a brief problem, not a distribution problem.
- Is conversion (form fill, trial signup, demo request, whatever the brief named) attributable to this piece? If attribution is missing, the UTM or analytics configuration is broken — not the content.
- If ranking is the goal: is the piece indexed and ranking for its target keyword? If not, the diagnostic order is: indexing → technical SEO → content quality for search intent → domain authority. Do not recommend content rewrites before confirming the piece is indexed.

**Measurement at 90 days:**
- Has the piece compounded? Content that performs at 30 days should perform better at 90 as search traffic compounds. A piece that peaks at 30 days and declines is often thin content — it captured some traffic but could not hold rankings against competitors.
- Have any distribution variants been tested? Email subject line A/B results, social variant performance, paid vs. organic split? If not, the measurement is incomplete — the piece may be underperforming in a channel while overperforming in another, with no signal back to brief decisions.

**Feedback loop (required, not optional):**
- Performance findings feed back to the content brief process: what angle performed, what format drove conversion, what distribution channel drove the most qualified traffic. This is documented in the content operations log, not just surfaced in a campaign post-mortem and forgotten.
- Underperforming pieces are diagnosed, not quietly archived. The diagnosis belongs in the brief process: was the brief wrong (wrong angle, wrong reader, wrong channel), the production wrong (quality issues), or the distribution wrong (wrong channel mix, inadequate amplification)?

**Who must sign off:** Distribution lead (distribution gate). Content ops and channel leads (30-day measurement review). Measurement review is a recurring editorial calendar item with a named owner — not a one-time check after publish.
<!--fold:ff37bc@end-->
PORTDOWN_8A5A77DB

# ── post ──
MARKER=$(awk '/^---$/ { f++; if (f==2) exit; next } f==1 && /^marker:[[:space:]]/ { sub(/^marker:[[:space:]]+/, ""); print; exit }' "$DEST")
[ -z "$MARKER" ] && { echo "seed: archive has no marker — corrupt" >&2; exit 1; }
awk -v m="$MARKER" -v outdir="$TARGET" '
  BEGIN {
    # Match <!--fold:<m>@file path="X"--> with an optional mode attr after
    # the path (fold emits  mode="644"  on executables).
    file_re = "^<!--fold:" m "@file path=\"([^\"]+)\"( mode=\"[0-9]+\")?-->$"
    end_re  = "^<!--fold:" m "@end-->$"
  }
  $0 ~ end_re { if (current) close(current); exit }
  $0 ~ file_re {
    if (current) close(current)
    line = $0
    sub(/^<!--fold:[^@]+@file path="/, "", line); sub(/".*$/, "", line)
    current = outdir "/" line
    dir = current; sub(/\/[^\/]*$/, "", dir)
    if (dir != current) system("mkdir -p \"" dir "\"")
    printf "" > current
    next
  }
  current { print >> current }
' "$DEST"
SEED_EXTRACTED=$(find "$TARGET" -type f -not -path "$DEST" 2>/dev/null | wc -l)
if [ "$SEED_EXTRACTED" = "0" ]; then
  echo "seed: archive contained no files — refusing to delete the source" >&2
  echo "  archive preserved at: $DEST" >&2
  exit 1
fi
rm -f "$DEST"

echo "" >&2
echo "✓ seed unpacked → $TARGET ($SEED_EXTRACTED files)" >&2
find "$TARGET" -type f | sort | while IFS= read -r _sf; do
  echo "  ${_sf#${TARGET}/}" >&2
done
echo "" >&2
if [ -f "$TARGET/SKILL.md" ]; then
  echo "This seed contains a skill (SKILL.md). Install it in your agent's skills directory." >&2
  echo "" >&2
fi
echo "Install the seed skill if not already installed:" >&2
echo "  https://seed.show/skill" >&2
echo "" >&2
echo "Publisher prompt:" >&2
sed 's/^/  /' >&2 <<'__SEED_PROMPT_END_AC1F2B__'
You have the content pipeline context. Read README.md for the mental model (pipeline as manufacturing, bottlenecks compound upstream), what agents get wrong, and what AI is changing. Read workflow.md for the eight-stage gate framework with decision criteria at each stage. Fetch sources.md for current methodology references — do not use platform-specific feature docs as methodology. To share your own context bundles: curl seed.show/skill | bash
__SEED_PROMPT_END_AC1F2B__
exit 0