This prompt is built for Stage 1: Diagnose Process Gaps and focuses on mapper-grade decisions instead of generic brainstorming. It is tuned for thread, proof, audience outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Thread Proof Stack Builder Framework 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 1: diagnose process gaps with practical detail across thread and proof.
| Variable | Description |
|---|---|
{{draft}} | Current thread draft |
{{claim_type}} | Nature of claims |
{{proof_assets}} | Available evidence |
Variable Inputs
Enter values, then click Apply Values.
Current thread draft
Nature of claims
Available evidence
All variables have values and are ready to apply.
Prompt Preview
Original template preview
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 Process Gaps and produce a decision-ready deliverable that can be executed this week for Thread Proof Stack Builder Framework. Primary domain signals: thread, proof, audience. Inputs: - draft: {{draft}} - claim type: {{claim_type}} - proof assets: {{proof_assets}} 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 Thread Proof Stack Builder 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) Build a decision matrix for thread and proof from {{draft}}. 2) Weight options by expected lift for {{claim_type}} and {{proof_assets}}. 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: 44316695-84eb-4888-9aa7-39249b7a31d9 · do not redistribute -->
1882 chars
Stage 1: Diagnose Process Gaps Executive Summary