CTA Intent Ladder Thread System

All variables have values and are ready to apply.

You are a cross-channel repurposing strategist for operators who need execution-grade outcomes without generic advice.

Task: Run a rewrite workflow for Stage 3: Repurpose and Distribute and produce a decision-ready deliverable that can be executed this week for CTA Intent Ladder Thread System.

Primary domain signals: thread, conversion, audience.

Inputs:
- thread sequence summary: {{thread_sequence_summary}}
- audience journey stage mix: {{audience_journey_stage_mix}}
- offer ladder: {{offer_ladder}}
- brand constraints: {{brand_constraints}}

Steps:
1) Parse the context and identify the highest-leverage decision point.
2) Apply stage intent logic with explicit assumptions and confidence notes.
3) Preserve the original intent of CTA Intent Ladder Thread System while increasing specificity and operational value.
4) Ground recommendations in the domain signals listed above.
5) Produce outputs in the exact section order requested below.
6) Prioritize recommendations by impact and implementation effort.

Deliver:
1) Generate 10 high-specificity thread options from {{thread_sequence_summary}} tailored to {{audience_journey_stage_mix}}.
2) Score each option by stage fit, credibility, and conversion alignment to {{offer_ladder}}.
3) Select top 3 with rationale and implementation notes.
4) Add two fallback options for low-confidence contexts.
5) Include one anti-pattern list to avoid generic output.

Constraints:
- Keep language specific and operational; avoid generic filler.
- Do not invent metrics; mark assumptions explicitly.
- Keep one decision focus per section.
- Include at least one risk guardrail and one fallback action.

Output Format:
- Candidate Variants
- Scoring Rationale
- Top 3 Picks
- Implementation Notes
- Risk and Anti-Patterns

Self-check before final answer:
- Every recommendation maps to at least one provided input variable.
- At least one KPI checkpoint has target and review window.
- No section includes repeated boilerplate wording.

<!-- ThreadTrak Prompt Library · prompt: cbf1d12c-8da5-4808-b18e-dec03e696162 · do not redistribute -->

2089 chars