Rishikesh Ranjan — rishikeshranjan.com

// disciplines

Repurpose

/ttm-repurpose

Fan out a long-form asset into derivative assets across channels with full brief-produce-verify per derivative. Use to maximize content reach.

manual invocation
allowed-tools:ReadWriteBashGlobGrepTask
SKILL.md ↗

Overview

Fan out a long-form hero asset into derivative assets across channels, running the full brief-produce-verify lifecycle on each derivative. The point is compound reach: most teams produce one-off assets, but the advantage comes from making one hero work across five channels (LinkedIn from a blog, email from a landing page, threads from a podcast transcript) while preserving the positioning invariant.

This is not a lightweight command. It runs the complete production lifecycle per derivative: a channel-adapted brief, a fresh production context, and independent verification through the gate wall, with explicit provenance so any channel asset traces back to its parent and brief. Invoke it with ttm-repurpose (optionally passing the source asset path), and it will analyze the source for repurposable segments, generate per-channel briefs from CHANNELS.md, produce each derivative wave-parallel, verify each one, and track them all as linked assets in the campaign.

The skill must be run within an existing campaign whose source asset already lives in a campaign's ASSETS/ directory, with the campaign in phase produced, verified, reviewed, fixed, or shipped.

How it works

The command reads and follows the workflow at ${CLAUDE_PLUGIN_ROOT}/workflows/discipline/repurpose.md. The required reading pulled in by that workflow includes ${CLAUDE_PLUGIN_ROOT}/references/context-loading.md, ${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md, and ${CLAUDE_PLUGIN_ROOT}/workflows/lifecycle/brief.md.

Step 0: First-run inline education

Read .taketomarket/CONFIG.md. Parse first_run_seen (object) and inline_education (boolean, default true).

If inline_education is false: skip this step. Else if first_run_seen.ttm-repurpose is not true, print the explainer below verbatim, then mark this skill as seen:

node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run mark ttm-repurpose

Use this exact check (bash) to decide whether to print: node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" first-run check ttm-repurpose --raw -- the JSON seen field is true once the explainer has run before.

Explainer for /ttm-repurpose

/ttm-repurpose takes a shipped hero asset and generates derivative assets for other channels (LinkedIn from a blog, email from a landing page, threads from a podcast transcript) while preserving the positioning invariant. Each derivative runs the full gate wall.

Why it matters: most marketing teams produce one-off assets; the compound advantage comes from making one hero work across five channels. Repurpose is the systematic version of that, with explicit provenance so you can trace any channel asset back to the parent and the brief.

(Canonical source: references/inline-education-blurbs.md. Embedded verbatim because workflows do not @-resolve files at runtime.)

Purpose

Fan out a long-form source asset into derivative assets across channels. Executes full brief-produce-verify per derivative with hero-first Task() orchestration. Each derivative gets a channel-adapted brief, fresh production context, and independent verification. This is NOT a lightweight command -- it runs the full production lifecycle per derivative.

Constraints

Campaign Context Required

This workflow MUST be run within an existing campaign context. The source asset must exist in a campaign's ASSETS/ directory with a campaign that is in phase: produced, verified, reviewed, fixed, or shipped.

Process

Text-Mode Detection

Text mode (--text flag): Set TEXT_MODE=true if --text is present in $ARGUMENTS or if the runtime is not Claude Code. When TEXT_MODE is active, replace every AskUserQuestion call with a plain-text numbered list.

Detection:

if echo "$ARGUMENTS" | grep -q -- '--text'; then TEXT_MODE=true; fi

If AskUserQuestion tool is not available in the current runtime, set TEXT_MODE=true. When TEXT_MODE is active, replace each AskUserQuestion with a plain-text numbered list:

[HEADER]
[QUESTION]
  1. [OPTION_1_LABEL] -- [OPTION_1_DESCRIPTION]
  2. [OPTION_2_LABEL] -- [OPTION_2_DESCRIPTION]
  ...
Type the number of your choice:

Step 1: Load Context

takeToMarket > LOADING REPURPOSE CONTEXT

Extract SOURCE_ASSET_PATH from $ARGUMENTS (strip --text flag if present):

SOURCE_ASSET_PATH=$(echo "$ARGUMENTS" | sed 's/--text//g' | xargs)

Read Tier 1 summaries from all 9 reference files (lines 1 to <!-- END_SUMMARY -->):

  • .taketomarket/POSITIONING.md
  • .taketomarket/BRAND.md
  • .taketomarket/ICP.md
  • .taketomarket/CHANNELS.md
  • .taketomarket/STATE.md (frontmatter only)
  • .taketomarket/CALENDAR.md
  • .taketomarket/COMPETITORS.md
  • .taketomarket/METRICS.md
  • .taketomarket/LEARNINGS.md

Read Tier 2 (full content) for production context:

  • .taketomarket/POSITIONING.md
  • .taketomarket/CHANNELS.md
  • .taketomarket/BRAND.md
  • .taketomarket/ICP.md

Step 2: Identify Source Asset

Parse SOURCE_ASSET_PATH from $ARGUMENTS.

Validate Path (T-10-11 mitigation)

Use path.resolve() equivalent to canonicalize the path, then verify:

  1. File exists at the specified path
  2. Path is within .taketomarket/CAMPAIGNS/ directory -- reject any path that does not resolve to a location under .taketomarket/CAMPAIGNS/[slug]/ASSETS/
  3. Campaign is in appropriate phase -- read the campaign's STATE.md and confirm phase is one of: produced, verified, reviewed, fixed, or shipped

Extract from the validated path and campaign data:

  • CAMPAIGN_SLUG -- extracted from the path (the directory name under CAMPAIGNS/)
  • SOURCE_ASSET_ID -- look up the source file in MANIFEST.json by matching the filename against hero.file and derivatives[].file entries. Extract the matching asset_id.
  • SOURCE_CHANNEL -- from the matching MANIFEST.json asset entry's channel field
  • SOURCE_CONTENT -- read the full file content

If validation fails at any step, display a specific error:

  • Path not found: "Source asset not found at [path]. Check the file path and try again."
  • Not in CAMPAIGNS: "Source asset must be within a .taketomarket/CAMPAIGNS/[slug]/ASSETS/ directory."
  • Wrong phase: "Campaign [slug] is in phase [phase]. Repurpose requires produced, verified, reviewed, fixed, or shipped."
  • Not in MANIFEST: "Source asset not found in MANIFEST.json. Was this asset produced by /ttm-produce?"

Step 3: Select Target Channels

Read .taketomarket/CHANNELS.md active channels list.

Parse all active channels from CHANNELS.md. Remove SOURCE_CHANNEL from the list (do not repurpose to the same channel the source was produced for). Default selection: all remaining active channels.

Ask user for channel selection (per D-12):

AskUserQuestion:
  title: "Repurpose Target Channels"
  question: "Repurpose to which channels? Default: all active channels minus source."
  options:
    - label: "All channels"
      description: "[list all remaining channels]"
    - label: "[channel 1]"
      description: "Repurpose to [channel 1] only"
    - label: "[channel 2]"
      description: "Repurpose to [channel 2] only"
    - label: "Custom selection"
      description: "Enter comma-separated channel numbers"
  • If user selects "All channels" or accepts the default: use all remaining active channels.
  • If user selects a specific channel: use only that channel.
  • If user selects "Custom selection": collect comma-separated numbers and resolve to channels.

Identify Hero Channel (per D-13)

From the selected target channels, identify the HERO_CHANNEL -- the channel with the highest reach baseline from CHANNELS.md metrics/baselines section. If baselines are not available or tied: use the first channel in the selected list.

Store HERO_CHANNEL and HERO_CHANNEL_SLUG (URL-safe version of channel name). Store remaining channels as REMAINING_CHANNELS.

Step 4: Generate Derivative Briefs

takeToMarket > GENERATING DERIVATIVE BRIEFS ([N] channels)

For each target channel, generate a channel-adapted derivative brief (per D-11). Read the source asset content and extract the core message/thesis. Cross-reference .taketomarket/CHANNELS.md for each target channel's configuration:

  • Format requirements (content type, structure)
  • Typical length/word count for the channel
  • Audience overlap with source channel

Cross-reference .taketomarket/BRAND.md for tone-per-context adjustments if defined for the target channel.

Write each brief with these sections:

  • Header: Derivative Brief title, source filename, campaign slug, source asset ID
  • Adaptation Requirements: Channel name, format (from CHANNELS.md), length, tone adjustment (from BRAND.md or "match source")
  • Core Message: Extract primary thesis, key claims, and CTA from source (must be preserved)
  • Channel-Specific Adaptations: Hook/opening, structure, length limits, CTA format, playbook rules
  • Positioning Anchor: Primary differentiator and proof points from POSITIONING.md (direct quote)
  • Outcome Metric: Inherit from campaign BRIEF.md, or channel-default from CHANNELS.md baselines

Write each brief to: .taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${CHANNEL_SLUG}.md

Step 5: Produce Hero Derivative

takeToMarket > REPURPOSING: HERO DERIVATIVE ([HERO_CHANNEL])

Read the agent prompt template from ${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md. Fill placeholders:

  • [BRIEF_PATH] --> .taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/REPURPOSE-BRIEF-${HERO_CHANNEL_SLUG}.md
  • [POSITIONING_PATH] --> .taketomarket/POSITIONING.md
  • [BRAND_PATH] --> .taketomarket/BRAND.md
  • [ICP_PATH] --> .taketomarket/ICP.md
  • [PLAYBOOK_PATH] --> resolved playbook for HERO_CHANNEL (from ${CLAUDE_PLUGIN_ROOT}/playbooks/${CHANNEL_TYPE}.md), or "none" if not found
  • [OUTPUT_PATH] --> .taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md
  • [ASSET_TYPE] --> derivative content type for this channel
  • [CHANNEL] --> HERO_CHANNEL name
  • [HERO_PATH] --> SOURCE_ASSET_PATH (the original source serves as the "hero" reference)

Also inject a "Source Asset Reference" section into the prompt with SOURCE_CHANNEL and SOURCE_ASSET_PATH so the producer can reference the original content.

Call Task() with the populated prompt. WAIT for Task() to complete before proceeding. After it returns, verify the hero derivative file exists and has content:

test -s ".taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-01-${HERO_CHANNEL_SLUG}.md"

If the file is empty or missing, error: "Hero derivative production failed -- file not written by subagent." and exit.

Step 6: Produce Remaining Derivatives (Wave-Parallel)

If only 1 target channel was selected (hero only): skip this step.

takeToMarket > REPURPOSING: DERIVATIVES ([N] channels, wave-parallel)

For each channel in REMAINING_CHANNELS:

  1. Read agent prompt template from ${CLAUDE_PLUGIN_ROOT}/agents/ttm-producer.md
  2. Assign sequential filename: R-[NN]-${CHANNEL_SLUG}.md where NN starts at 02
  3. Fill all placeholders (same pattern as Step 5, with channel-specific values and [HERO_PATH] pointing to the hero derivative R-01-${HERO_CHANNEL_SLUG}.md)
  4. Inject Source Asset Reference (same as Step 5)
  5. Call Task() with the populated prompt

All derivative Task() calls run in parallel (per D-13 wave-parallel pattern). After ALL Task() calls complete, verify each output file exists and has content (> 50 chars):

test -s ".taketomarket/CAMPAIGNS/${CAMPAIGN_SLUG}/ASSETS/R-${NN}-${CHANNEL_SLUG}.md"

For any derivative that failed (file empty or missing):

  • Log warning: takeToMarket > WARNING: Derivative R-${NN}-${CHANNEL_SLUG}.md failed
  • Continue with remaining assets. Do NOT abort the repurpose run.

Track successful and failed derivatives for the manifest and completion banner.

Step 7: Verify Derivatives

takeToMarket > VERIFYING DERIVATIVES

For each successfully produced derivative, run simplified inline gate checks. Run 3 simplified gates per derivative (PASS / WARN / FAIL each):

  1. Positioning Drift -- maintains primary differentiator, claims trace to proof points, no must-not-say terms
  2. Format Correctness -- meets channel length constraints, has required structural elements (hook, CTA), follows channel conventions
  3. Voice Drift -- matches BRAND.md voice archetype, no banned words, tone consistent with source

Record results as VERIFY_RESULTS array with per-derivative gate outcomes. If any FAIL: flag for user attention but do NOT auto-fix. Recommend /ttm-fix or /ttm-verify.

Step 8: Update MANIFEST.json

takeToMarket > UPDATING MANIFEST

Read existing MANIFEST.json to determine the next available asset_id. Find the maximum asset_id across hero.asset_id and all derivatives[].asset_id. Set NEXT_ID = max_id + 1.

Build DERIVATIVES_JSON array -- one entry per successfully produced derivative, each with asset_id (sequential from NEXT_ID), name, type: "derivative", channel, and file. Run the campaign.cjs CLI to update MANIFEST.json:

node "${CLAUDE_PLUGIN_ROOT}/bin/ttm-tools.cjs" campaign repurpose-manifest "${CAMPAIGN_SLUG}" ${SOURCE_ASSET_ID} '${DERIVATIVES_JSON}'

Verify the command succeeded (exit code 0 and output contains derivatives_added).

Step 9: Completion Banner

Display a banner with:

  • Source asset name and channel
  • Campaign slug
  • Derivative count (successful / attempted)
  • Per-derivative table: #, Channel, File, Positioning result, Format result, Voice result
  • Warnings for any failed productions or FAIL gate results
  • Manifest and brief file paths
  • Next steps: /ttm-verify, /ttm-review, /ttm-fix

Step 10: Final humanization (MANDATORY)

Every audience-facing asset MUST pass through /ttm-humanize before write. For each draft asset produced in this phase:

  1. For each derivative produced (long-form -> short-form, email -> social, etc.), invoke /ttm-humanize <derivative-path> via the Skill tool.
  2. Wait for the rewritten version.
  3. Write the humanized output to the final asset destination.
  4. Do not write the un-humanized draft.

Internal state files (campaign briefs, manifests, STATE.md) are exempt.

Success criteria

  • Source asset validated (exists, in campaign, campaign in correct phase)
  • Channel selection defaults to all active minus source, with user override
  • Hero derivative produced first (blocking) in highest-reach channel
  • Remaining derivatives produced in wave-parallel via Task()
  • Each derivative gets a channel-adapted brief cross-referencing CHANNELS.md
  • Simplified verification (positioning drift, format, voice) runs per derivative
  • All derivatives tracked in MANIFEST.json with source_asset_id
  • Completion banner with per-derivative verification results
  • Each derivative passed through /ttm-humanize before write.

Output

  • .taketomarket/CAMPAIGNS/${SLUG}/REPURPOSE-BRIEF-*.md (per-channel derivative briefs)
  • .taketomarket/CAMPAIGNS/${SLUG}/ASSETS/R-*.md (produced derivative assets)
  • .taketomarket/CAMPAIGNS/${SLUG}/MANIFEST.json (updated with derivative entries)

What if this doesn't fit?

Looks like /ttm-repurpose can't do that yet.

  • Want a new skill? /ttm-request-skill
  • Existing skill needs work? /ttm-improve-skill