Newsletter Engine

Newsletter Engine — Full Newsletter Production Pipeline

An agent team collaborates to produce newsletters through the pipeline of curation → writing → A/B testing → editing → publishing, all at once.

Execution Mode

Agent Team — 5 members communicate directly via SendMessage and cross-validate each other's work.

Agent Roster

Workflow

Phase 1: Preparation (Performed directly by the orchestrator)

1. Extract from user input:
   • Topic/Theme: The subject the newsletter will cover
   • Newsletter Info (optional): Brand tone, subscriber count, publication frequency
   • Target Reader (optional): Subscriber characteristics, interests
   • Constraints (optional): Length, specific section requirements
   • Existing Files (optional): Content, previous issues, etc. provided by the user
2. Create the _workspace/ directory at the project root
3. Organize the input and save it as _workspace/00_input.md
4. If existing files are provided, copy them to _workspace/ and skip the corresponding phase
5. Determine the execution mode based on request scope

Phase 2: Team Assembly and Execution

Inter-agent communication flow:

• curator complete → deliver angles & content to copywriter, trending keywords to analyst
• copywriter complete → deliver A/B variant materials to analyst, draft to editor-in-chief
• analyst complete → deliver send optimization & A/B recommendations to editor-in-chief
• editor-in-chief complete → deliver final version to quality-reviewer
• reviewer cross-validates all deliverables. On 🔴 Must Fix: request revision → rework → re-validate (up to 2 rounds)

Phase 3: Integration and Final Deliverables

1. Verify all files in _workspace/
2. Confirm all 🔴 Must Fix items have been addressed
3. Report the final summary to the user:
   • Curation Brief — 01_curation_brief.md
   • Newsletter Draft — 02_newsletter_draft.md
   • A/B Test Plan — 03_ab_test_plan.md
   • Editor-in-Chief Final — 04_editorial_final.md
   • Review Report — 05_review_report.md

Scope-Based Modes

Using Existing Files: If the user provides content or a previous newsletter, copy it to the appropriate location in _workspace/ and skip that phase.

Data Transfer Protocol

File naming convention: {order}_{deliverable}.{extension}

Error Handling

Test Scenarios

Happy Path

Prompt: "Create a weekly newsletter covering AI industry trends. Target audience: developers. Tone: professional with wit" Expected Results:

• Curation: 5+ latest AI articles, trend analysis, recommended resources
• Copy: Subject line (A/B 2 variants), preheader, intro + main story + sub stories + resources + closing
• Analysis: 2 A/B tests (subject line, CTA), send time recommendations, performance forecast
• Editorial: Tone review, legal check, final version
• Review: All consistency matrix items verified

Existing File Flow

Prompt: "Make a newsletter from this collection of articles" + content file attached Expected Results:

• Existing content organized into _workspace/01_curation_brief.md
• Edit Mode: copywriter + editor-in-chief + quality-reviewer deployed
• curator skipped

Error Flow

Prompt: "Just design A/B tests for this newsletter subject line" Expected Results:

• Switch to Analysis Mode (analyst + quality-reviewer)
• No newsletter body exists, so analyst proposes subject-line-pattern-based A/B variants
• Review report notes "body copy/curation not generated"

Agent Extension Skills

Each agent leverages the following extension skills to enhance deliverable quality: