Post Score Normalization Framework

This prompt is built for Stage 2: Angle and Narrative Design and focuses on generator-grade decisions instead of generic brainstorming. It is tuned for threads, conversion, content outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Use Thread Quality Preflight Checker to drive execution.. Use it when you need immediate execution clarity and trustworthy next-step recommendations.

Use Case

Use when you are running content qa scorecards workflow and need a high-confidence generator output for stage 2: angle and narrative design with practical detail across threads and conversion.

Input Variables

Variable	Description	Example
`{{content_format_mix}}`	Formats that need consistent scoring	threads, single tweets, visual captions
`{{current_scoring_issues}}`	Observed inconsistency problems	threads score too high, captions score too harshly
`{{quality_objective}}`	Primary reason for normalization	improve scoring reliability across weekly reviews
`{{reviewer_setup}}`	Who performs content QA	founder plus one editor

Prompt Template

Variable Inputs

Enter values, then click Apply Values.

Formats that need consistent scoring

Observed inconsistency problems

Primary reason for normalization

Who performs content QA

All variables have values and are ready to apply.

Prompt Preview

Original template preview

You are a narrative and positioning strategist for operators who need execution-grade outcomes without generic advice.

Task: Run a plan workflow for Stage 2: Angle and Narrative Design and produce a decision-ready deliverable that can be executed this week for Post Score Normalization Framework.

Primary domain signals: threads, conversion, content.

Inputs:
- content format mix: {{content_format_mix}}
- current scoring issues: {{current_scoring_issues}}
- quality objective: {{quality_objective}}
- reviewer setup: {{reviewer_setup}}

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 Post Score Normalization 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 threads options from {{content_format_mix}} tailored to {{current_scoring_issues}}.
2) Score each option by stage fit, credibility, and conversion alignment to {{quality_objective}}.
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: 25fba113-055d-470f-8441-1d3e2dd1db0f · do not redistribute -->

2077 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 2: Angle and Narrative Design 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

Run calibration on 5 historical posts before adoption. This reveals where anchors are too vague or too strict. Run a 7-day checkpoint review, compare output quality against baseline, and iterate only one major variable per cycle.

contentqascoringcalibrationquality-control