← Registry

Weekly content pipeline

Three agents turn your team's Slack ideas into a researched, edited draft every Monday.

By DamonVersion 10 installsUpdated Sep 30, 2026

Connects ToSlackSlack

What it does

Every Monday at 9:00 three agent steps run in sequence:

  1. Research: reads the last 7 days of #content-ideas in Slack, skips ideas already covered in the Content folder of your drive, picks one that fits the audience in Content/brand-voice.md, researches it on the web and writes Content/<date>-<slug>/brief.md: the angle, 5–8 key points each with a source link, and what existing articles miss.
  2. Write: drafts draft.md from the brief only, following Content/brand-voice.md.
  3. Edit: edits the draft in place, checks every claim against the brief, and writes editor-notes.md with what changed and what couldn't be verified, plus a suggested meta description and LinkedIn post.

A final step messages you the title, the source idea, the file paths and the editor's notes. Nothing is posted or published.

What you need

  • Slack connected, and a channel where your team drops content ideas.
  • A Content/brand-voice.md in your drive: audience, tone, words to avoid, length, and a sample of on-brand writing.

Customize it

  • Assign a different agent to each step (a researcher, a writer, an editor), each with its own personality. The template ships with the default agent in all three.
  • Change the channel name in the research step.
  • Add a fourth step that cuts the draft into social posts.
  • Auto-approve file.write for this workflow so it runs unattended.

What It Does, Step by Step

  1. Step 1Trigger

    Runs every Monday at 9:00 AM (America/New_York)Runs every Monday at 9:00.

  2. Step 2Agent

    You are the researcher. Read Content/brand-voice.md in the drive for the audience. Read the last 7 days of messages in the Slack channel #content-ideas. Skip any idea already covered by a folder in Content/. Pick the one idea with the most reactions or replies that fits the audience. Research it on the web, preferring primary sources. Write Content/<YYYY-MM-DD>-<slug>/brief.md containing: the working title, the angle in two sentences, 5-8 key points each with a source link, what existing articles on the topic miss, and who in Slack suggested the idea. Do not write prose for the article. Say plainly where evidence is thin. Return the path of the brief.

    UsesSlack
  3. Step 3Agent

    You are the writer. Read the brief at the path from the previous step and Content/brand-voice.md. Write the article as draft.md in the same folder, following the brand voice exactly: its audience, tone, heading style and target length. Use only claims that are in the brief, with their source links. Prefer concrete examples to general statements. Return the path of the draft.

    UsesSlack
  4. Step 4Agent

    You are the editor. Read the draft at the path from the previous step, the brief in the same folder, and Content/brand-voice.md. Cut first: remove filler, repetition and throat-clearing. Check every factual claim against the brief; fix any that overstate their source and flag any you cannot verify. Fix style issues directly in draft.md. Write editor-notes.md in the same folder listing what you changed and what still needs a human check, then a suggested meta description under 160 characters and a suggested LinkedIn post under 120 words. Return the title, the folder path and the notes.

    UsesSlack
  5. Step 5Send a Message

    Open a thread titled "Content draft" with the article title. Post the source idea and who suggested it, the draft's folder path, and the editor's notes, with anything needing a human check first. If no idea was picked this week, post one line saying so.

More from Damon

See All

WorkflowProductivity

Daily inbox digest

Every morning, summarize what landed in your inbox and flag what needs a reply.

Gmail

Damon

WorkflowSales

Monday pipeline review

Every Monday, list the deals that have gone quiet and suggest a next step for each.

HubSpot

Damon

WorkflowProductivity

Weekly status report

Every Friday, write the project status report from your project tool and offer to post it.

Linear

Damon