Repeatable Viral Seed Engine

This prompt is built for Stage 4: Execution Blueprint and focuses on generator-grade decisions instead of generic brainstorming. It is tuned for conversion, audience outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Convert top opportunities into executable plans.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.

Use Case

Use when you are running viral pattern analysis workflow and need a high-confidence generator output for stage 4: execution blueprint with practical detail across conversion and audience.

Input Variables

Variable	Description	Example
`{{core_narrative_pillars}}`	Core content narrative anchors	positioning, conversion mechanics, execution systems
`{{audience_question_bank}}`	Recurring audience questions	top objections and recurring practical questions
`{{performance_feedback_loop}}`	How performance data is fed back	weekly metric review plus post-level qualitative notes
`{{weekly_output_target}}`	Expected weekly concept volume	20 seed ideas and 6 high-priority test candidates

Prompt Template

Variable Inputs

Enter values, then click Apply Values.

Core content narrative anchors

Recurring audience questions

How performance data is fed back

Expected weekly concept volume

All variables have values and are ready to apply.

Prompt Preview

Original template preview

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

Task: Run a package workflow for Stage 4: Execution Blueprint and produce a decision-ready deliverable that can be executed this week for Repeatable Viral Seed Engine.

Primary domain signals: conversion, audience.

Inputs:
- core narrative pillars: {{core_narrative_pillars}}
- audience question bank: {{audience_question_bank}}
- performance feedback loop: {{performance_feedback_loop}}
- weekly output target: {{weekly_output_target}}

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 Repeatable Viral Seed Engine 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 conversion options from {{core_narrative_pillars}} tailored to {{audience_question_bank}}.
2) Score each option by stage fit, credibility, and conversion alignment to {{performance_feedback_loop}}.
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: 2920ffc7-71d0-462d-a3dc-00c3605b4bb5 · do not redistribute -->

2097 chars

Tip: Adjust variable values, click Apply Values, confirm the preview, then use the top-right copy button.

Copy & Open in ThreadTrak

Example Output

Stage 4: Execution Blueprint Candidate Variants

Variant A: specific angle with proof-led opener.
Variant B: contrarian framing with explicit audience filter.
Variant C: utility-first framing with conversion CTA. Scoring Rationale

Variant B wins on differentiation (9/10) and conversion fit (8/10). Implementation Notes
Publish B first; test A as fallback within 48h. Risk and Anti-Patterns
Avoid broad claims without proof examples.

Tips

Archive losing seeds with context so future cycles avoid repeating low-fit concept types. Track one KPI baseline before launch, run a 7-day checkpoint review, and iterate one major variable per cycle to preserve signal quality.

idea-generationengineviral-ideasiterationsystems