This prompt is built for Stage 2: System Design and focuses on mapper-grade decisions instead of generic brainstorming. It is tuned for content, conversion, offer outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Persona Voice Calibrator System to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running multi-outcome workflow b07 and need a high-confidence mapper output for stage 2: system design with practical detail across content and conversion.
| Variable | Description |
|---|---|
{{team}} | Who executes |
{{goals}} | Publishing goals |
{{offer_focus}} | Offer priority |
{{time_budget}} | Available time |
Variable Inputs
Enter values, then click Apply Values.
Who executes
Publishing goals
Offer priority
Available time
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 Daily Content Ops Console Engine. Primary domain signals: content, conversion, offer. Inputs: - team: {{team}} - goals: {{goals}} - offer focus: {{offer_focus}} - time budget: {{time_budget}} 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 Daily Content Ops Console 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) Build a decision matrix for content and conversion from {{team}}. 2) Weight options by expected lift for {{goals}} and {{offer_focus}}. 3) Rank top opportunities with confidence levels. 4) Add sequencing and ownership for the first execution sprint. 5) Include one fallback branch for uncertain signals. 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: - Decision Matrix - Weighted Rankings - Recommended Path - Execution Sequence - Fallback Branch 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: 5f47d8e1-e97b-4367-8e7c-31f35e706a7d · do not redistribute -->
1879 chars
Stage 2: System Design Executive Summary