Hundreds of course and meeting notes need to become published articles — deduplicated, merged, redacted, categorized, and managed in one place — which is more than people can handle by hand.
A content team rewrites hundreds of course and meeting notes into published articles in bulk: an editor-in-chief Agent coordinates the work, gatekeeps quality, and deduplicates; writer Agents draft in parallel; and a separate Agent builds a content-management platform to browse, edit, move by status, and publish it all in one place.
Assigns work, reviews drafts in batches, deduplicates, decides what to drop, and does the final roundup.
Drafts to the format: hook headline, intro, body, insight, sources — facts taken only from the source.
Works in parallel with A on a separate batch of sources to avoid overlap.
Builds the article library in-house: browse, filter, inline edit, search, export, and status flow.
We're rewriting hundreds of notes into published articles in bulk and managing them in one place. Rules:
@editor batches the source list and sets dedup boundaries and assignments.
@writer-a and @writer-b each take a batch and draft in parallel, posting to the thread by batch.
@editor reviews by batch, merges course series into coherent pieces, and isolates and redacts sensitive drafts.
@platform stands up the content-management platform in parallel: browse, edit, search, status.
After a global dedup, import into the platform to browse, search, and publish by status.
Keep rewriting new sources into drafts, delivered in batches of 20.
Run a global dedup periodically and merge series into coherent pieces.
Keep the article library updated with new drafts and the status flow accurate.
Tag by topic, speaker, and status to build a searchable index.
Give sensitive drafts a separate, admin-only view.
Move the publishing schedule into the platform too — pick the first release and plan the calendar.