Content Repurposing

---
name: content-repurposing
description: Transform a newsletter, video, meeting, podcast, article, or report into distinct channel-native posts, emails, scripts, clips, carousels, or summaries.
---

# Content Repurposing

Create native assets from one proven source without chopping it into repetitive fragments.

## Job contract

- Owns: cross-format or multi-channel transformation.
- Does not own: one named Instagram carousel (`instagram-carousel-maker`), same-format updates (`content-refresher`), or style cleanup alone (`de-slop`).
- Finished deliverable: source map and complete channel-ready assets.

## Workflow

1. Read the complete source and identify its thesis, proof, scenes, examples, useful details, and rights constraints.
2. Establish target audience, channels, number of assets, objectives, and format limits.
3. Build an angle map. Each asset needs a distinct reader job, source moment, and payoff, not merely a new hook.
4. Define the native craft constraints for each channel: reader context, opening behaviour, length, pacing, structure, visual or spoken needs, and CTA conventions.
5. Draft from the source's strongest scenes, mechanisms, examples, tensions, or consequences. Do not reduce the source to generic tips.
6. Preserve the writer's recognisable voice markers while adapting the structure to the channel. Do not replace their voice with a generic platform voice.
7. Keep claims traceable to the source. Label new interpretation.
8. Revise once for specificity and difference: remove generic hooks, unsupported advice, repeated proof, repeated conclusions, and lines that could belong to any creator.
9. Deliver complete publish-ready drafts, but do not publish without approval.

## Craft bar

- Each asset must give the audience a different reason to care, not the same lesson in a different length.
- Use a concrete scene, example, mechanism, or consequence when the source contains one.
- Match the channel without imitating its worst habits: avoid empty hook formulas, listicle rhythm, forced questions, and filler CTAs.
- When the source is too thin to support the requested number of strong assets, produce fewer and explain why.

## Output

```markdown
# Repurposing Package

## Source Truth
[Thesis, proof, reusable scenes, constraints]

## Angle Map
| Asset | Reader job | Distinct angle | Source proof |

## Finished Assets
[Complete channel-specific drafts]

## Accuracy And Rights Check
[Claims, quotes, permissions, attribution]

## Repetition Check
[How assets differ beyond wording]
```

## Guardrails

- Never invent examples, customer stories, quotes, or performance claims.
- Do not strip qualifications from the source to make a stronger hook.
- Do not auto-publish, schedule, send, or upload.