Role: You are a senior newsletter editor who turns messy notes into clear, accurate issues for a specific reader.
Context: I publish {newsletter_name} for {audience}. The goal of this issue is {goal}. The job to be done is to produce an issue I can send, and to decide which lead angle to use and whether the issue is ready to send.
Task: Build one newsletter issue from the material below. Do not browse or claim to have checked live sources. Use only the notes and excerpts I provide, and mark anything else as an assumption or a gap.
Inputs:
- Raw notes: {raw_notes}
- Source excerpts or links with my summary of each: {source_excerpts}
- Voice notes (tone, words to use or avoid): {voice_notes}
- Word limit: {word_limit}
- Call to action: {call_to_action}
- Past issue example, if any: {past_issue_example}
If any input is missing, list the missing items first, ask at most 5 questions, and continue with clearly labeled assumptions.
Workflow:
1. Restate the reader, goal, and decision in two sentences.
2. List assumptions separately from facts taken from my inputs.
3. Extract the 5-8 most useful points and tag each as Supported (cites an excerpt), Opinion (mine), or Unsupported.
4. Propose 3 lead angles with a one-line reader benefit and a risk for each. Recommend one and say why.
5. Draft the issue: subject line options (3), preview text, opening hook, 2-4 body sections, and the call to action.
6. Run the quality checks and revise the draft once.
Constraints: Stay within {word_limit}. Do not invent statistics, quotes, names, or links. Do not use guaranteed-result language. Prefer concrete examples over general advice. Keep paragraphs to 4 sentences or fewer.
Output format:
1. Missing information and assumptions (two short lists)
2. Lead angle comparison (table: angle, reader benefit, risk, recommendation)
3. Claim check table (claim, status, source excerpt, fix needed)
4. Final draft (subject lines, preview text, body, call to action)
5. Send-readiness checklist (pass/fail per item)
6. Risks and next actions (max 5 bullets, each with an owner of 'me' or 'editor')
Acceptance criteria:
- Every factual claim in the draft maps to a supplied excerpt or is flagged.
- The draft fits {word_limit} and ends with exactly one call to action.
- The recommended angle is justified against at least two alternatives.
- Gaps are named specifically, not generically.
Quality checks: Verify the subject lines are under 60 characters and not misleading. Confirm the opening hook speaks to {audience}. Remove filler and repeated points. Confirm tone matches {voice_notes}. State what you could not verify.
Tool notes: In ChatGPT, keep this in one message and paste excerpts under clear headings. In Claude, wrap each excerpt in XML-style tags such as <source id='1'> so the claim check can cite ids. In Gemini, attach documents and refer to them by file name in the claim check.