Content routines

Drafts on a cadence, publication on your terms.

Content routines do the recurring half of publishing: researching a topic into a sourced draft, or turning merged pull requests into release notes grouped by user impact. Publication stays with a human or an explicitly approved tool, so the schedule produces reviewable drafts, not surprises on your blog.

Routines in content

• Weekly

  Blog research and drafting

  Keep a publication schedule alive with sourced drafts that only need human review, not a rewrite.

• Twice a month

  Release notes draft

  Ship release notes that describe user impact, assembled from what actually merged.

Works with

• R

  Resend

  Send approved drafts, digests, and recurring customer updates through a bounded email surface.

• GH

  GitHub

  Read repositories and issues, then open reviewable pull requests through GitHub's remote MCP server.

See every integration

Common questions

Will a content routine publish without review?

Not unless you explicitly approve a publishing tool and mark it for automatic execution. By default a run ends with a draft and a trace of the sources it used.

How does it keep our voice?

Voice and structure live in the routine instructions and skills you configure, and they persist across every run. When a draft misses, you edit the instructions once rather than re-briefing a writer.

Where does the research come from?

From the sources the routine is allowed to read — your repository, approved research sources, or public pages. Drafts cite what they used so review starts from evidence.