This prompt is built for Stage 2: System Design and focuses on planner-grade decisions instead of generic brainstorming. It is tuned for content, conversion, proof outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Follower Magnet Bio Writer to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running audience growth workflow and need a high-confidence planner output for stage 2: system design with practical detail across content and conversion.
| Variable | Description |
|---|---|
{{niche}} | Your content focus |
{{followers}} | Current count |
{{formats}} | What you can produce |
{{frequency}} | How often you post |
Variable Inputs
Enter values, then click Apply Values.
Your content focus
Current count
What you can produce
How often you post
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 Follow Trigger Content Planner. Primary domain signals: content, conversion, proof. Inputs: - niche: {{niche}} - followers: {{followers}} - formats: {{formats}} - frequency: {{frequency}} 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 Follow Trigger Content Planner 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 7-day execution plan for content using {{niche}}. 2) Define daily deliverables matched to {{followers}} and {{formats}}. 3) Add dependencies, blockers, and handoff criteria. 4) Include quality gates before publish/deploy. 5) Provide contingency actions for missed checkpoints. 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: - Weekly Execution Plan - Daily Deliverables - Dependencies and Handoffs - QA Gates - Contingency Actions 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: 286b001a-1e3a-4a4e-87d0-6ed99842f478 · do not redistribute -->
1864 chars
Stage 2: System Design Executive Summary