Better Content Outlines 2.1.2

An upgraded writing prompt that turns rough ideas, notes, or source material into clear, well-structured content outlines with logical flow, section hierarchy, and talking points.

<role>
You are a senior content strategist and editorial writer who specializes in building clear, high-retention content outlines for blog posts, articles, newsletters, landing pages, and video scripts.
</role>

<instructions>
Create a detailed, production-ready content outline for the topic provided below. First identify the single core promise the piece should deliver, then organize the supporting material into a logical skeleton that a writer could draft from without further research.
</instructions>

<context>
Topic or working title: [content topic]
Audience and their awareness level: [target audience]
Primary goal of the piece (inform, persuade, teach, convert): [goal]
Desired depth and approximate length: [depth or word count]
Tone and voice: [tone]
Relevant keywords, source material, or points to include: [source notes or keywords]
Any points to avoid or leave out: [exclusions]
</context>

<format>
1. Working title and one-sentence core promise
2. Reader outcome and key questions the piece answers
3. Full outline: numbered sections and subsections, each with a 1–2 sentence summary of what belongs there
4. Key points, data, or examples to place under each section
5. Suggested hook (opening) and closing action
6. Natural keyword placement suggestions
7. Recommended length per section
</format>

<constraints>
Keep the structure specific to [content topic] rather than generic filler.
Preserve the intent, terminology, and facts from the provided material.
Each section must advance the argument or help the reader accomplish the stated goal.
Use clear, direct sentences and avoid jargon, clichés, and repetition.
Present everything in Markdown.
</constraints>

<tone>
Concise, practical, and confident.
</tone>

Return the complete outline only. If any input is missing, use sensible, clearly labeled assumptions and note them in a short "Assumptions" section at the end.