Write & communicate

Generate accurate headlines and openings

Create compelling entry points that accurately preview the content, evidence, and reader value

6 min setupTested with:ChatGPTReviewed: 2026-08-28
1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Generate accurate headline-and-opening pairs for the supplied content.

Draft, claim, evidence, qualifiers, examples, and unknowns:
[content]

Audience situation, awareness, question, value, action, and objections:
[reader]

Channel, length limits, voice, SEO phrase, prohibited tactics, and criteria:
[constraints]

Identify what the content actually proves, teaches, or helps the reader do. Generate strategically distinct angles such as direct benefit, question, tension, specific method, evidence, mistake, or audience situation only when the body fulfills them. Pair each title with an opening that immediately continues the same promise and supplies necessary context. Preserve scope, sample, timeframe, uncertainty, and causal boundaries. Do not invent urgency, novelty, secrets, popularity, outcomes, personal experience, numbers, or consensus. Avoid vague curiosity gaps, fear, absolutes, and superlatives unless directly supported. For each pair state angle, intended reader, body evidence that fulfills it, possible misleading interpretation, and risk. Rank by accuracy, specificity, relevance, differentiation, and channel fit; explain why the top pair wins.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Content and evidence
Article explains a five-field handoff audit: requester, owner, accepter, acceptance evidence, escalation. A two-week observation in one five-person content team reviewed 12 recurring handoffs and found 4 without named accepters; accepters were then added. No measured effect on speed or errors. Article teaches the audit and labels the observation as a single-team example.
Reader and purpose
New small-team managers whose tasks stall in review. They want a quick diagnostic, not a new software recommendation. Desired action: audit one recurring handoff.
Channel constraints
Blog title up to 60 characters and opening up to 45 words. Plain professional voice. SEO phrase 'handoff checklist' if natural. No 'ultimate,' 'secret,' guarantee, fear, or productivity claims. Success means qualified readers continue to the checklist.

Example output

  1. Method angle — recommended Title: “A five-field handoff checklist for stalled reviews” Opening: “When work sits at ‘ready,’ the missing detail may be who can accept it. This checklist helps a small-team manager inspect requester, owner, accepter, acceptance evidence, and escalation—without assuming another tool will fix the workflow.” Fulfillment: the complete article teaches all five fields. Risk: “stalled” could imply the checklist fixes delays; the opening correctly frames it as inspection.

  2. Question angle Title: “Who accepts the work after the owner finishes?” Opening: “An assignee can complete a task while the handoff remains undefined. Start by separating the person doing the work from the person authorized to accept it, then test four related fields.” Fulfillment: owner-versus-accepter distinction and full audit. Low risk.

  3. Evidence angle Title: “What 12 handoffs revealed in one small team” Opening: “Over two weeks, one five-person content team reviewed 12 recurring handoffs and found four without a named accepter. This is a single-team example, not a benchmark; it shows how to run the same five-field check.” Fulfillment: exact observation with scope. Medium risk because readers may still overgeneralize, so the qualifier must remain.

Pair 1 ranks first because it matches search intent, states the usable method, names the relevant situation, and does not depend on a small sample for appeal. Exclude “Stop review delays with this checklist” because no outcome effect was measured.

Why this works

  1. 1

    Pairing the opening with the title tests whether the promised idea can actually continue.

  2. 2

    A misleading-interpretation check catches technically true but deceptive framing.

Check the result

  • Does the body directly fulfill every title and opening promise?

  • Are scope, qualification, and evidence unchanged?

  • Are top pairs strategically distinct rather than synonym swaps?

More ways to explore

Where this recipe fits

Keep the work moving

Organize information 6 min setup

Generate a source-grounded FAQ

Turn source material into useful questions and traceable answers without filling evidence gaps

A prioritized FAQ with source locators, answer status, and unresolved questions
Open recipe