Skip to content

rampstackco/claude-skills / skills/content-repurposing

content-repurposing

Verified

Cross-format content adaptation. Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts) without losing the original's value or producing AI-slop variants. The discipline of adaptation per medium rather than mass-blast distribution. Triggers on content repurposing, content adaptation, cross-format content, content atomization, content multiplication, content distribution across formats, source-piece-to-derivative, video shorts from blog, email from whitepaper, podcast from article, blog series from research. Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats, when repurposing is happening but the derivatives feel mass-produced, or when AI-assisted repurposing is producing slop variants of strong source pieces.

references/sequencing-and-cadence-patterns.md

View on GitHub
# Sequencing and cadence patterns

When to release derivatives relative to the source. Concentrated vs distributed cadence. Pacing audits. The patterns that match cadence to the source's traffic curve and audience attention.

The release sequence and cadence determine how the cross-format set lands. The wrong sequencing can produce a wave of derivatives that exhausts audiences, or a trickle that loses connection to the source's authority. The right sequencing matches the source's traffic curve and the audiences' attention rhythm.

---

## Sequencing patterns

Three patterns for how derivatives sequence relative to the source.

### Source-first, derivatives following

**The pattern.** The source piece publishes; derivatives roll out over the following 2-12 weeks. The source carries the initial authority and traffic spike; derivatives extend reach and re-engage audiences over time.

**Strengths.**

- The source piece's launch is concentrated, earning the full attention of the program's audiences. The launch is a moment.
- Derivatives reference the source's authority. Each derivative can link back to the source as the canonical version; the source's ranking and authority compounds.
- Audiences who engaged with the source are primed for derivatives; the first derivative often performs well because the audience is warm.

**Weaknesses.**

- The source needs to support the launch with strong promotion. If the source publishes quietly, the launch moment is muted.
- Audiences who missed the source see derivatives without context; the derivatives need to stand alone.

**Fits.** Most programs. The default sequencing pattern.

### Simultaneous launch

**The pattern.** Source and a wave of derivatives publish on the same day. Multiple channels fire at once.

**Strengths.**

- Maximum splash. The cross-format presence on a single day signals significance to audiences.
- Cross-channel reinforcement. Audiences encountering the program on multiple channels in one day register the significance more strongly than serial encounters.

**Weaknesses.**

- Risks audience fatigue. If every channel is firing the same day, audiences may tune out before they engage with any individual piece.
- Heavy production load on launch day. All derivatives must be ready simultaneously, which can compress quality.
- Less time for individual derivatives to land. Each derivative competes for attention with every other derivative on the same day.

**Fits.** Major flagship launches where the moment itself is part of the value (annual research reports, ebook releases, manifesto-style pieces). Tier 1 source pieces.

### Derivatives-first, source as anchor

**The pattern.** Social posts and short-form video tease ideas; the source piece publishes as the synthesizing flagship after the buildup.

**Strengths.**

- Builds anticipation. Audiences who engage with the early derivatives expect the source piece.
- The source piece publishes into a primed audience.

**Weaknesses.**

- Less common; works only for built-up audiences who follow the program closely.
- Risks giving away too much before the source. If the early derivatives expose the source's argument, the source publishes into an audience that feels they have already read it.
- Coordination overhead. The cross-format buildup needs to land at the right cadence to support the source's launch.

**Fits.** Programs with engaged audiences and strong social presence. Less common than source-first; specific to programs that have earned anticipation.

---

## Cadence within the rollout

Three pacing patterns within the chosen sequencing.

### Concentrated cadence

**The pattern.** Most derivatives ship within 4-6 weeks of source.

**Strengths.**

- Maximum momentum from the source's authority. The source's traffic curve is highest in the first 2-4 weeks; derivatives launching during that window benefit from the source's freshness.
- The cross-format set feels coherent. Audiences see the program everywhere within a short window; the campaign feeling earns engagement.
- Easier to coordinate. Production and scheduling concentrate; the team is in launch mode for a defined period.

**Weaknesses.**

- Limited time for individual derivatives to land. A derivative in week 5 has less attention available than the source did in week 1.
- Audience fatigue risk. Audiences may disengage before week 4-6 if the cadence feels relentless.
- Less long-tail value. After week 6, the cross-format set largely stops producing new touchpoints.

**Fits.** Tier 1 and Tier 2 source pieces. Programs running flagship launches where the campaign nature is part of the strategy.

### Distributed cadence

**The pattern.** Derivatives ship over 3-6 months.

**Strengths.**

- Each derivative has space to land. No internal competition for audience attention.
- Long-tail value. The program continues to produce touchpoints over a longer window.
- Sustainable. The team is not in launch mode for months; production fits steady-state cadence.

**Weaknesses.**

- Risk of losing connection to source. By month 3, the source piece may be background context rather than the active reference.
- Less momentum. The campaign feeling fades; each derivative is a standalone moment rather than part of a coherent push.
- Coordination overhead extended. Owners and producers need to maintain focus across months.

**Fits.** Evergreen flagship pieces with sustained traffic curves. Programs with smaller production capacity that cannot sustain concentrated cadence.

### Indefinite cadence

**The pattern.** Derivatives keep being created from the source as long as the source remains relevant.

**Strengths.**

- Maximum long-term value extraction.
- Adapts to audience response. Derivatives that perform well inform what to produce next; the program learns from the cross-format set's reception.

**Weaknesses.**

- Most programs cannot sustain indefinite attention to a single source. Discipline tends to decay.
- Risk of voice drift. Derivatives produced 12 months apart may have voice variation that the original launch cadence avoided.
- Less coherent campaign feel. Audiences see scattered derivatives over a long window without a clear narrative.

**Fits.** Truly evergreen sources whose value compounds for years. Rare; usually reserved for major flagship pieces (defining manifestos, definitive research reports).

---

## Pacing audits

Match cadence to the source's traffic curve and the audience's attention rhythm.

**The source's traffic curve.**

- **Sharp early traffic, fast decay.** Trending-topic pieces, news-driven analysis. Concentrated cadence; the audience is paying attention for a short window.
- **Sustained high traffic for weeks.** Flagship reports on hot topics. Concentrated to mid-distributed cadence; the audience attention extends but eventually fades.
- **Slow build, sustained traffic for months.** Evergreen flagship pieces, definitive guides. Distributed cadence; the audience encounter is continuous over time.
- **Sustained low traffic with occasional spikes.** Reference pieces that get rediscovered. Indefinite cadence works if the production capacity supports it.

**The audience's attention rhythm.**

- **Email subscribers.** Engagement varies; sequences spaced 5-7 days work for most B2B; daily for high-engagement consumer audiences.
- **Social audiences.** Platform-specific. LinkedIn rewards 1-2 posts per week from program accounts; X rewards higher frequency; Instagram somewhere in between.
- **Podcast audiences.** Episodic; weekly cadence common; bi-weekly works for higher-production-effort shows.
- **YouTube audiences.** 1-2 videos per week typical for active channels; long-form video can be less frequent.

**The pacing decision.** Match the source's traffic curve and the audiences' attention rhythm. If they conflict, the source's curve usually wins; the cross-format set's coherence depends on the source's authority window.

---

## Sequencing and cadence per derivative type

Some derivatives have natural sequencing within the rollout.

**Derivatives that should ship early.**

- Email teaser or preview email. Sets up the source's launch with the email audience.
- Social posts that announce the source. Visibility on launch day.
- Short-form video that introduces the topic. Algorithmic recommendation responds best when the content is fresh.

**Derivatives that should ship 1-3 weeks in.**

- First blog post in a series. The source piece is still drawing traffic; the blog post benefits from internal linking and the audience's continued interest.
- Webinar based on the source. Allows time for audience registration and promotion.
- First batch of social pull-quote posts. The source's themes are familiar; the pull quotes resonate.

**Derivatives that should ship 1-3 months in.**

- Podcast episode. Production cycle is longer; podcast audience overlap with source audience may be partial.
- Subsequent blog posts in a series. Distributed cadence; each post earns its own attention.
- Email sequence (if not the immediate teaser). The sequence develops the source's framework over time.

**Derivatives with flexible timing.**

- FAQ extractions and AI-search snippets. These can ship at source-launch or any time after; AI search citation accumulates over months.
- Ebook consolidation. Often ships 6-12 months after source pieces accumulate; the consolidation work itself takes time.

---

## Common sequencing and cadence failures

**All-at-once dumping.** A wave of 12 derivatives in 5 days. Audiences disengage by day 3; most derivatives produce little engagement. Cure: distributed cadence with audience-attention spacing.

**Source quietly publishing while derivatives ship loudly.** The derivatives carry the launch but the source piece itself launches without the attention it deserves. Cure: source-first launch with promotion focused on the source; derivatives follow.

**Source publishing months after promised derivatives.** Derivatives that previewed a coming source piece ship; the source publishes 4 months later. Audiences have lost connection. Cure: tighten production schedule or flip the sequencing to source-first.

**Cadence too aggressive for the audience.** Email subscribers receiving daily emails for 2 weeks unsubscribe. Cure: match cadence to audience attention norms; email audiences typically tolerate 1-2 sends per week from a program.

**Cadence too slow.** Distributed cadence stretched too long; by month 4, audiences have forgotten the source. Cure: bring cadence closer to source's traffic curve; consider indefinite cadence only when the source genuinely supports it.

**No sequencing plan.** Derivatives ship as they happen to be ready, with no coordination. Cross-format set feels random; audiences see scattered touchpoints with no coherent narrative. Cure: even rough sequencing planning at production time produces better outcomes than no plan.

---

## Methodology-level choices that stay in the public skill

The three sequencing patterns, the three cadence patterns, the pacing audit, the per-derivative-type sequencing, the common failures.

## Implementation choices that stay internal

Specific calendar tooling. Specific automation that schedules derivatives across channels. Specific coordination workflows between producers and channel owners. Specific A/B testing of cadence variants. The team's own conventions for fast-track vs queued derivatives. These vary by team and tooling.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall