Audience Question Harvester Generator Framework

This prompt is built for Stage 3: Execution Blueprint and focuses on generator-grade decisions instead of generic brainstorming. It is tuned for audience, conversion, offer outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Build recurring series and pillars from proven winning angles. Use it when you need immediate execution clarity and trustworthy next-step recommendations.

Use Case

Use when you are running you are betting on weak ideas - find winning angles in 60 minutes and need a high-confidence generator output for stage 3: execution blueprint with practical detail across audience and conversion.

Input Variables

Variable	Description	Example
`{{niche}}`	Your niche	Freelance web design
`{{level}}`	Audience knowledge level	Mix of wannabe freelancers and established designers wanting to grow
`{{problems}}`	Common pain points	Finding clients, pricing projects, handling difficult clients, scaling beyond solo
`{{offers}}`	What you sell	Freelance accelerator course ($299) and 1-on-1 coaching ($500/mo)

Prompt Template

Variable Inputs

Enter values, then click Apply Values.

Your niche

Audience knowledge level

Common pain points

What you sell

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 3: Execution Blueprint and produce a decision-ready deliverable that can be executed this week for Audience Question Harvester Generator Framework.

Primary domain signals: audience, conversion, offer.

Inputs:
- niche: {{niche}}
- level: {{level}}
- problems: {{problems}}
- offers: {{offers}}

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 Audience Question Harvester Generator 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 audience options from {{niche}} tailored to {{level}}.
2) Score each option by stage fit, credibility, and conversion alignment to {{problems}}.
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: 718c38ee-b105-4111-92d2-136e850caba2 · do not redistribute -->

1959 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 3: 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

Start with buying questions when you're doing a product launch. Start with beginner questions when growing your audience. Track one KPI baseline before launch, run a 7-day checkpoint review, and iterate one major variable per cycle to preserve signal quality.

questionsresearchaudienceideation