matteotitta Content operations
Take a completed content strategy and operationalize it. Design series arcs, sequence content across channels, build the production pipeline, and optimize per channel. This skill builds the system; downstream skills create individual assets.
When to use
Invoke when user says: "operationalize this content strategy", "content operations / pipeline / calendar for {company}", "serialize our pillars", "how do we produce content at scale?", "set up content production workflow", "content cascade planning", "turn this strategy into a production system".
Do NOT invoke when: building the strategy itself (use content-strategy), creating individual posts (use linkedin-content, youtube-scripts), running a full founder LinkedIn program (use founder-linkedin), auditing existing content (use content-audit).
Inputs
| Input | Required? | Source |
|---|---|---|
| Content strategy (pillars, funnel mix, channels, volume targets, series themes) | Required | content-strategy output |
| TOV guidelines | Recommended | tov-guidelines output |
| Team capacity (people, hours) | Recommended | User |
| Tool stack (Notion, Scripe, Canva, etc.) | Recommended | User |
| Existing calendar, performance data, lead capture setup, CRM details, budget | Optional | User |
Validate before proceeding: strategy with pillars + funnel mapping; channel selection defined; volume targets set; at least one of TOV / team capacity / tool stack. If strategy missing, run content-strategy first. Can proceed with pillars + channels minimum, but flag gaps.
Process
Four phases. Each ends in a checkpoint that gates the next phase. Detailed step-by-step protocols, templates, and tables live in the premium reference.
Phase 1 — Content serialization → the premium reference
Turn strategic pillars into executable multi-part series with narrative arcs.
- Design series arcs per pillar — 1-3 series per pillar, picking arc type (problem / mechanism / case-study / framework / opinion) per the premium reference (series architecture framework).
- Define installment structure — hook escalation, knowledge progression, callback structure, cadence.
- Map funnel-stage formats — assign each series to TOFU / MOFU / BOFU; verify mix matches strategy ratios (typical 40/35/25).
- Create series tracking framework — status, installments published, performance, decision triggers (TWE > 2 → expand; < 0.5 → retire).
Checkpoint: every pillar has 1+ series with clear arc; installments show progression; funnel mapping verified; tracking ready.
Phase 2 — Cross-channel sequencing → the premium reference
Orchestrate how content flows across channels over time.
- Design cascade rules — anchor → derivatives per channel with timing and adaptation rules. Targets 80% cascade efficiency (1 anchor → 6-10 derivatives) per the cascade efficiency model in the premium reference.
- Define channel cadence — weekly rhythm per channel, coordinated cross-channel timing.
- Map cross-channel coordination — lead / amplification / conversion channel roles + stagger rules.
- Build calendar planning protocol — Sunday review checklist, backlog management (evergreen / timely / launch queues), buffer rules (2-week minimum, 1 reactive slot/week).
Checkpoint: cascade map complete, weekly rhythm defined per channel, channel roles assigned, Sunday review checklist documented.
Phase 3 — Production pipeline & team → the premium reference
Build the operational mechanics — Kanban pipeline, team roles, handoff workflows.
- Define pipeline stages — Idea Backlog → Briefed → Draft → Review → Approved → Scheduled → Published → Analyzed, with owner + exit criteria per stage.
- Specify card fields — pillar, funnel stage, channel, format, series, owner, due date, source, derivative parent.
- Map team roles + time commitments — Content Lead / Writer / Designer / QA, scaled to Solo / Small / Full team. For solo: collapse Lead + Writer + QA into one person; designer freelance or AI-assisted.
- Define handoff workflows — text content, video content, graphics content (each with stage-by-stage routing).
Checkpoint: pipeline stages set with exit criteria, card fields specified, roles adapted to team size, handoffs documented per content type.
Phase 4 — Channel optimization & lead capture → the premium reference
Make content work harder per platform, then capture results into pipeline.
- Apply channel algorithm optimization — LinkedIn (360 Brew, Jan 2026: saves 5x likes, dwell time, no external links, first 90 min, no edits), YouTube (title+thumbnail, watch time, first 30s, SEO), Newsletter (subject line < 50 chars, Tue/Thu mornings, deliverability, UTMs), Podcast (title SEO, first 2 min, cross-promo).
- Configure lead capture — 6 methods mapped to tools: engagement tracking (Trigify/Valley), profile views (Sales Nav), lead magnets (beehiiv/ConvertKit), connection downloads, website visits (RB2B/Clearbit), direct bookings (Cal.com).
- Define retargeting triggers — warm DM, newsletter CTA, retargeting ads, email flow, connection request, content follow-up. Enrichment flow: capture → Clay → ICP score → CRM with content attribution tag.
Checkpoint: optimization applied per platform, capture methods configured with data flow, retargeting triggers defined with downstream skill references, enrichment flow documented.
Self-evaluation
- Every pillar has at least one executable series?
- Cascade rules map anchor → derivatives for all active channels?
- Pipeline stages clear with ownership + handoffs?
- Channel optimization grounded in platform-specific evidence (cite source where possible)?
- Realistic for stated team capacity?
If issues: flag gaps, mark assumptions, do not invent performance data.
Review gate (Level 2)
Present series plan, cascade map, pipeline, calendar, and optimization. Actions: [Approve] [Adjust] [Refine].
Output
Use the standard playbook template in the premium reference (sections: series plan → cross-channel sequence → production pipeline → channel optimization & lead capture). Pre-delivery checklist + worked examples + anti-examples + iteration prompts also in that file.
Chain suggestions
After approval: linkedin-content (execute LinkedIn series), youtube-scripts (video series), social-selling (lead capture plays), outreach-emails (email retargeting flows), linkedin-infographics (graphic derivatives).
Final ship gate
Run /premortem --output before ship. See /premortem skill for the 5 execution domains (will-it-resonate / will-it-convert / will-it-stay-on-brand / will-stakeholder-push-back / will-it-degrade-over-time) and output template.
Trivial-case escape: ## Premortem\nNo failure modes — trivial change satisfies the contract for genuinely trivial outputs.