# /distribution-repurpose — Content Repurposing Pipeline

## Usage
```
/distribution-repurpose                     # Repurpose latest shipped idea
/distribution-repurpose {idea-id}           # Repurpose specific shipped idea
/distribution-repurpose --content="..."     # Repurpose arbitrary content
```

## Input
- `$ARGUMENTS` — optional: idea ID or content to repurpose

## Process

### Step 1: Load Source Content
1. If idea ID provided, read from `data/ideas.json`
2. If no argument, find the most recently shipped idea
3. Read `data/positioning.json` — messaging pillars for consistent voice
4. Read `data/social.json` — understand which platforms are active

Extract from source:
- **Title/headline** — the main hook
- **Key insight** — what's new/interesting
- **Target audience** — who cares about this
- **Technical details** — for dev-focused channels
- **Business impact** — for business-focused channels
- **Visual assets** — screenshots, diagrams, ship cards

### Step 2: Generate Channel-Specific Adaptations

For each active channel, create a tailored version:

#### Twitter/X Thread (5-7 tweets)
- Tweet 1: Hook — the most surprising/valuable insight
- Tweet 2-5: Story arc — problem → solution → result → detail
- Tweet 6: Takeaway or lesson learned
- Tweet 7: CTA with link + UTM
- Use patterns from `ai-content-generator.ts` (hooks, engagement patterns)
- Queue: `social-draft-thread-{topic}`

#### LinkedIn Post (Professional angle)
- Opening line: Pattern interrupt or contrarian take
- Body: "Here's what I learned building [feature]..."
- Formatting: Short paragraphs, line breaks, no hashtag spam
- CTA: Soft — "What's your experience with [topic]?"
- Queue: `copy-social-linkedin`

#### Reddit Post (Value-first, subreddit-adapted)
- Title: Question or insight format (NOT promotional)
- Body: Genuine story, metrics shared transparently, lessons learned
- Adapt tone to target subreddit (technical for r/programming, casual for r/SideProject)
- Link in context only, never as main content
- Queue: idea with tags ["growth", "reddit", "{subreddit}"]

#### Google Ads Keyword Group
- Map content to search intent keywords
- If content solves a problem → target "[problem] solution" keywords
- If content is a comparison → target "[product] vs [competitor]" keywords
- Queue: `copy-ad-google-{keyword}`

#### Meta Retargeting Ad
- Target: People who visited the content page but didn't convert
- Creative: Key visual from the content + social proof
- CTA: Return to complete signup
- Queue: `copy-ad-meta-retargeting-{content-slug}`

#### Email Newsletter Segment
- Subject line: Hook adapted for email (curiosity gap)
- Body: Summary with "read more" link
- Segment: Users interested in [topic]
- Queue: `email-blast-{campaign-slug}` or include in next digest

#### Indie Hackers / Dev.to Post
- Longer form, more transparent about metrics and journey
- Include code snippets if technical
- End with question to encourage discussion
- Cross-post with canonical URL to own blog

### Step 3: UTM Attribution Matrix
Each adaptation gets consistent tracking:

| Channel | utm_source | utm_medium | utm_campaign |
|---------|-----------|-----------|-------------|
| Twitter/X | twitter | social | {content-slug} |
| LinkedIn | linkedin | social | {content-slug} |
| Reddit | reddit | community | {content-slug} |
| Google Ads | google | cpc | {content-slug} |
| Meta Ads | meta | paid | retarget-{content-slug} |
| Email | email | newsletter | {content-slug} |
| Indie Hackers | indiehackers | community | {content-slug} |
| Dev.to | devto | blog | {content-slug} |

### Step 4: Publishing Schedule
Stagger publishing for maximum reach:

| Day | Channel | Why |
|-----|---------|-----|
| Day 0 | Twitter thread | Immediate, test the hook |
| Day 1 | LinkedIn post | Business hours reach |
| Day 2 | Reddit post | Different audience, value-first |
| Day 3 | Email newsletter | Owned channel, reliable |
| Day 5 | Dev.to / IH post | Long-form, search indexed |
| Day 7 | Google Ads | If content validates search intent |
| Ongoing | Meta retargeting | Runs continuously for page visitors |

### Step 5: Output
Create ideas in `data/ideas.json` for each channel adaptation:
- Category: "growth"
- Tags: ["growth", "repurpose", "{channel}", "{source-idea-id}"]
- Implementation plan with channel-specific content draft
- Success metrics: channel-specific (impressions, clicks, referral signups)
- Queue relevant tasks for each channel

Print summary:
- Source content: [title]
- Adaptations generated: [count]
- Channels covered: [list]
- Tasks queued: [list]

## Output Files
- `data/ideas.json` — repurposed content campaign ideas