---
name: content-pipeline-architect
description: Design and build automated content production pipelines. Takes a topic, brand voice, and target platforms, then generates a complete content calendar, platform-optimized posts, and an automation workflow plan. Ideal for social media, YouTube, blogs, and newsletters.
---

# Content Pipeline Architect

Design a complete automated content production pipeline from a single topic or brief, producing platform-specific content and an automation plan.

## Steps

### 1. Gather Requirements

Collect the following from the user (ask if not provided):

- **Topic or brief**: What the content is about
- **Brand voice**: Professional, casual, technical, friendly, authoritative, etc.
- **Target platforms**: Which subset of: Twitter/X, LinkedIn, Instagram, YouTube, Blog, Newsletter, TikTok
- **Cadence**: How often content should be published (daily, 3x/week, weekly)
- **Content pillars**: 3-5 recurring themes or categories (ask user to define, or suggest based on topic)

If the user gives a minimal brief (e.g., "content about AI tools"), infer reasonable defaults and state your assumptions.

### 2. Generate Content Calendar

Create a 2-week content calendar in table format:

```
## Content Calendar (Week 1-2)

| Day | Platform | Content Type | Topic/Angle | Content Pillar |
|-----|----------|-------------|-------------|----------------|
| Mon | Twitter  | Thread (5-7) | [specific angle] | [pillar] |
| Mon | LinkedIn | Article      | [specific angle] | [pillar] |
| Tue | Blog     | Long-form    | [specific angle] | [pillar] |
| ...
```

Rules for the calendar:
- **Vary content types**: Mix threads, single posts, carousels, long-form, short-form, video scripts
- **Cross-pollinate**: Repurpose one piece across platforms (e.g., blog → Twitter thread → LinkedIn post)
- **80/20 rule**: 80% value-giving content, 20% promotional
- **Platform-native**: Each platform gets content formatted for its norms and algorithm preferences

### 3. Generate Platform-Specific Content

For each entry in the calendar, produce the actual content:

#### Twitter/X
- Thread format: Hook tweet + 4-6 value tweets + CTA tweet
- Each tweet under 280 characters
- Use line breaks for readability
- End with a call to action (follow, reply, retweet)

#### LinkedIn
- Professional tone, 150-300 words
- Hook in first 2 lines (before "see more" fold)
- Use line breaks every 1-2 sentences
- End with a question to drive engagement
- 3-5 relevant hashtags

#### Instagram
- Caption: Hook + value + CTA, 150-200 words
- Include carousel slide text if applicable (8-10 slides, 1 key point per slide)
- 20-30 hashtags (mix of broad, niche, branded)

#### YouTube
- Title (60 chars max, keyword-rich)
- Description (200+ words, timestamps, links)
- Script outline: Hook (0-30s) → Problem (30-90s) → Solution (90-300s) → CTA (300-330s)
- 5 tags

#### Blog
- SEO-optimized title (60 chars)
- Meta description (155 chars)
- Outline with H2/H3 headers
- Target word count: 1,200-2,000 words
- Internal/external linking suggestions

#### Newsletter
- Subject line (50 chars, curiosity-driven)
- Preview text (90 chars)
- Sections: Hook → Main content → Quick wins → CTA
- Target: 500-800 words

### 4. Build Automation Workflow Plan

Design the automation pipeline using n8n (or similar):

```
## Automation Workflow

### Trigger
- [Schedule/webhook/manual trigger]

### Pipeline Steps
1. **Content Generation**: [AI model] generates drafts from content calendar
2. **Review Queue**: Drafts go to [Slack/email/Notion] for human review
3. **Approval Gate**: Approved → schedule, Rejected → revision loop
4. **Platform Publishing**:
   - Twitter: via Twitter API v2
   - LinkedIn: via LinkedIn API
   - Instagram: via Meta Graph API (or Buffer/Later)
   - YouTube: via YouTube Data API
   - Blog: via CMS API (WordPress/Ghost/Webflow)
   - Newsletter: via Mailchimp/ConvertKit API
5. **Analytics Collection**: Pull engagement metrics 24h/48h/7d after publish
6. **Performance Report**: Weekly summary of best/worst performing content

### Required API Keys
- [List each platform's API/OAuth requirements]

### n8n Nodes
- Schedule Trigger → HTTP Request (AI API) → IF (approval) → HTTP Request (platform APIs) → Wait → HTTP Request (analytics)
```

### 5. Output Deliverables Summary

Provide a final summary:

```
## Pipeline Summary

**Content produced**: X pieces across Y platforms
**Cadence**: [schedule]
**Automation level**: [fully automated / semi-automated with review gate / manual with templates]

### Deliverables
1. Content Calendar (2-week plan)
2. Platform-specific content (ready to post)
3. Automation workflow design (n8n-compatible)
4. API integration requirements

### Next Steps
- [ ] Set up API keys for target platforms
- [ ] Import n8n workflow template
- [ ] Review and customize generated content
- [ ] Schedule first batch
```

## Edge Cases

- **Single platform only**: Skip the cross-platform repurposing. Go deeper on that one platform with more varied content types.
- **No brand voice defined**: Default to "professional but approachable" and state the assumption.
- **B2B vs B2C**: Adjust tone, platform priority, and content depth based on audience type.
- **Regulated industries**: Add compliance review step to the automation pipeline.
- **Large volume (daily across 5+ platforms)**: Recommend a content batching strategy — produce a week's content in one session, then schedule.