## TL;DR

An RSS feed is already a structured content source; drafting from it is mostly plumbing.
The review step is what keeps quality up: auto-draft, human or agent approve.
Applies to blogs, changelogs, and release feeds.

## The query

```text
RSS to newsletter: auto-drafting from your feed
```

## Use this when

- You publish regularly via a blog, changelog, or release feed.
- You want a newsletter without manual curation each time.
- A human or agent reviews drafts before sending.

## Not for

- You publish less than monthly (a manual newsletter is simpler).
- There is no RSS feed for the content (build the feed first).
- You want fully automatic sending with no review (drafts without review drift into noise).

## Steps

1. Poll the feed on a schedule and diff against the last seen item IDs.
   Expected output: A list of new items since the last run, with no duplicates.
2. For each new item, extract the title, summary, and link into a draft issue template.
   Expected output: A draft newsletter with one section per new item.
3. Add a one-line editorial note per item: why it matters to the reader.
   Expected output: Drafts that read curated, not scraped.
4. Queue the draft for review and send on approval.
   Expected output: A sent newsletter that took minutes of review instead of hours of writing.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_aVDJjgy6fmnqHbuyt9S5qQ