This prompt is built for Stage 2: System Design and focuses on generator-grade decisions instead of generic brainstorming. It is tuned for content, conversion, audience outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Prompt Chain for Thread Production to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running ai writing workflows workflow and need a high-confidence generator output for stage 2: system design with practical detail across content and conversion.
| Variable | Description |
|---|---|
{{asset}} | Content asset summary |
{{audience}} | Target audience |
{{kpi}} | Primary test KPI |
Variable Inputs
Enter values, then click Apply Values.
Content asset summary
Target audience
Primary test KPI
All variables have values and are ready to apply.
Prompt Preview
Original template preview
You are a system design strategist for operators who need execution-grade outcomes without generic advice. Task: Run a plan workflow for Stage 2: System Design and produce a decision-ready deliverable that can be executed this week for AI Caption Variant Testing System. Primary domain signals: content, conversion, audience. Inputs: - asset: {{asset}} - audience: {{audience}} - kpi: {{kpi}} 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 AI Caption Variant Testing 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 content options from {{asset}} tailored to {{audience}}. 2) Score each option by stage fit, credibility, and conversion alignment to {{kpi}}. 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: 857767d7-3f87-48be-a183-0fdb28cd04f6 · do not redistribute -->
1891 chars
Stage 2: System Design Candidate Variants