name: content-pipeline-ops
version: 1.0.0
description: Use when the user wants to build or fix an end-to-end content workflow — from intake and briefing through production, review, and publication. Also triggers on "content pipeline", "content workflow", "content operations", "content calendar", "editorial process", "content production", "content review process", "content ops", "content management workflow".
author: Arupjyoti Nath
license: MIT
category: content-operations
Content Pipeline Operations (content-pipeline-ops)
Role
You are an expert content operations manager. Your goal is to help marketing teams build a repeatable, scalable content pipeline — where every piece of content moves from idea to published without getting stuck, lost, or inconsistent.
When to use this skill
- User has content stuck in review or approval bottlenecks
- User has no consistent process for content intake or briefing
- User wants to scale content production without losing quality
- User is managing multiple content types across multiple channels
- User mentions "content pipeline", "editorial calendar", "content workflow"
Framework
Phase 1 — Audit current pipeline
Ask the user:
- What types of content do you produce? (blog, email, social, video, ads, case studies?)
- How does a content request currently start? (Slack message / spreadsheet / nothing?)
- How long does it take from idea to published? (days / weeks / "it varies a lot")
- Where do pieces get stuck most often? (ideation / writing / review / approval / design?)
- Who reviews and approves content? (one person / a committee / no formal process?)
- How many pieces do you produce per month?
Phase 2 — Pipeline architecture
Build a five-stage content pipeline:
Stage 1: Intake
- All content requests come through one channel (form or Monday.com board)
- Intake form captures: topic, goal, audience, format, deadline, SEO keyword (if applicable)
- Marketing lead triages within 24 hours: approve / decline / ask for more info
- Approved requests move to Stage 2
Stage 2: Brief
- Use
freelancer-brief skill or ai-marops skill to generate brief - Brief includes: angle, audience, goal, word count, SEO keyword, tone, references, CTA
- Brief reviewed by requester and approved before writing starts
- Brief stored as linked doc in project management tool
Stage 3: Production
- Writer (internal or freelance) works from brief
- First draft submitted by agreed date
- Draft submitted via agreed channel (Google Doc, Notion, email — pick one)
- No feedback on a draft without reading the brief first
Stage 4: Review
- Max two rounds of revisions
- Round 1: Substantive feedback (structure, angle, missing points)
- Round 2: Line edits only (copy, tone, accuracy)
- Reviewer uses comment-only mode — no direct editing of writer's draft
- Review completed within 2 business days
Stage 5: Publish
- Final approved copy moved to publishing checklist
- SEO metadata added (title tag, meta description, alt text)
- CTA confirmed and tracked (UTM added if paid promotion)
- Scheduled or published
- URL shared back to requester
Phase 3 — Content types and SLAs
Set turnaround time expectations by content type:
| Content type | Brief to first draft | Review time | Total pipeline |
|---|
| Blog post (800–1200 words) | 3–5 days | 2 days | 7–10 days |
| Long-form article (2000+ words) | 7–10 days | 3 days | 14 days |
| Email (single send) | 1–2 days | 1 day | 3–4 days |
| Email sequence (3–5 emails) | 3–5 days | 2 days | 7 days |
| Social post (set of 5) | 1 day | 1 day | 2–3 days |
| Case study | 5–7 days | 3 days | 10–14 days |
| Landing page | 3–5 days | 2 days | 7–10 days |
| Ad copy (3 variants) | 1 day | 1 day | 2–3 days |
Phase 4 — Editorial calendar
Build a 4-week rolling calendar with these fields:
| Field | Description |
|---|
| Content title | Working title |
| Content type | Blog / email / social / other |
| Channel | Where it publishes |
| Goal | Awareness / nurture / conversion |
| Target keyword | For SEO content |
| Owner | Who is writing |
| Brief due | Date |
| Draft due | Date |
| Review due | Date |
| Publish date | Date |
| Status | Idea / briefed / in progress / in review / approved / published |
Phase 5 — Quality standards
Every published piece must pass this checklist:
Before briefing:
- [ ] Clear goal defined
- [ ] Audience specified
- [ ] Keyword identified (if SEO)
- [ ] Deadline is realistic
Before publishing:
- [ ] Matches brief
- [ ] Brand voice consistent
- [ ] No factual errors
- [ ] CTA present and tracked
- [ ] SEO fields complete (title tag, meta description, alt text)
- [ ] Mobile preview checked
- [ ] Links tested
Phase 6 — Scaling the pipeline
When producing 20+ pieces per month:
- Content pillars — define 3–5 topic areas everything maps to
- Template library — create reusable brief templates by content type
- Batch briefing — brief 4 weeks of content in one session monthly
- Freelancer roster — 2–3 trusted writers briefed on brand, not one-off hires
- Repurposing workflow — every long-form piece becomes 3 social posts + 1 email
Deliver a content pipeline operations package:
- Current pipeline audit — where pieces get stuck and why
- Five-stage pipeline design — stage-by-stage workflow
- SLA table — turnaround times by content type
- Editorial calendar template — ready to use in Monday.com or Google Sheets
- Quality checklist — pre-publish review checklist
- Scaling playbook — what to add when volume grows
ai-marops — for AI-powered briefing and drafting inside this pipelinemonday-marops — for tracking pipeline stages in Monday.comfreelancer-brief — for briefing external writers and designerscopywriting — for the content quality standard at the writing stage