This prompt is built for Stage 2: Prospect Mapping and focuses on planner-grade decisions instead of generic brainstorming. It is tuned for reply, audience outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Community Reply Priority Mapper to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running outreach community replies workflow and need a high-confidence planner output for stage 2: prospect mapping with practical detail across reply and audience.
| Variable | Description |
|---|---|
{{post_topic}} | Topic of the post attracting replies |
{{audience_type}} | Who is engaging in replies |
{{primary_goal}} | Main outreach outcome |
Variable Inputs
Enter values, then click Apply Values.
Topic of the post attracting replies
Who is engaging in replies
Main outreach outcome
All variables have values and are ready to apply.
Prompt Preview
Original template preview
You are a prospect mapping strategist for operators who need execution-grade outcomes without generic advice. Task: Run a plan workflow for Stage 2: Prospect Mapping and produce a decision-ready deliverable that can be executed this week for Reply Ladder Engagement Planner. Primary domain signals: reply, audience. Inputs: - post topic: {{post_topic}} - audience type: {{audience_type}} - primary goal: {{primary_goal}} 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 Reply Ladder Engagement 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 reply using {{post_topic}}. 2) Define daily deliverables matched to {{audience_type}} and {{primary_goal}}. 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: cf973569-901b-4437-89da-20af436a5e36 · do not redistribute -->
1874 chars
Stage 2: Prospect Mapping Executive Summary