Community Reply Priority Mapper

All variables have values and are ready to apply.

You are a diagnostic strategy operator for operators who need execution-grade outcomes without generic advice.

Task: Run a triage workflow for Stage 1: Diagnose Segment and Offer Fit and produce a decision-ready deliverable that can be executed this week for Community Reply Priority Mapper.

Primary domain signals: reply.

Inputs:
- reply samples: {{reply_samples}}
- community objective: {{community_objective}}
- time available: {{time_available}}

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 Community Reply Priority Mapper 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 reply and diagnose from {{reply_samples}}.
2) Weight options by expected lift for {{community_objective}} and {{time_available}}.
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: 24af8b28-f07a-4c0c-9661-6e4ce10613fc · do not redistribute -->

1922 chars