This prompt is built for Stage 1: Diagnose Audience Signal and focuses on generator-grade decisions instead of generic brainstorming. It is tuned for thread, conversion, content outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Thread Hook Variation Rapid Lab to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running thread hook cta testing workflow and need a high-confidence generator output for stage 1: diagnose audience signal with practical detail across thread and conversion.
| Variable | Description |
|---|---|
{{variant_pool}} | Hook and CTA combinations to test |
{{baseline_performance_assumptions}} | Expected starting performance ranges |
{{exposure_constraints}} | Limits on how many tests can run |
{{decision_horizon}} | Timeframe for selecting winners |
Variable Inputs
Enter values, then click Apply Values.
Hook and CTA combinations to test
Expected starting performance ranges
Limits on how many tests can run
Timeframe for selecting winners
All variables have values and are ready to apply.
Prompt Preview
Original template preview
You are a diagnostic strategy operator for operators who need execution-grade outcomes without generic advice. Task: Run a triage workflow for Stage 1: Diagnose Audience Signal and produce a decision-ready deliverable that can be executed this week for Thread Hook CTA Multi Arm Bandit Simulator Framework. Primary domain signals: thread, conversion, content. Inputs: - variant pool: {{variant_pool}} - baseline performance assumptions: {{baseline_performance_assumptions}} - exposure constraints: {{exposure_constraints}} - decision horizon: {{decision_horizon}} 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 Thread Hook CTA Multi Arm Bandit Simulator Framework 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 {{variant_pool}} tailored to {{baseline_performance_assumptions}}. 2) Score each option by stage fit, credibility, and conversion alignment to {{exposure_constraints}}. 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: 34e18c1e-19b5-4ec8-8c17-4f55ac797e61 · do not redistribute -->
2128 chars
Stage 1: Diagnose Audience Signal Candidate Variants