Work on Repeat
Menu

Example routine

Weekly topic brief (workflow)

Research a topic, draft the brief, then package it for sending — three ordered stages in one run.

Use this routine

Suggested rhythm

Weekly

0 9 * * 4

America/Los_Angeles

Expected result

A packaged weekly brief with a subject line, three evidence-backed developments, and a closing recommendation.

Built for

Content · Marketing

Works with

  • Firecrawl

What the routine does

## Stage 1 of 3: Research Research {{topic}} for {{audience}}. Gather what changed in the last week from approved sources, separate verified facts from interpretation, and list each finding with its source link. Do not draft any prose yet. ## Stage 2 of 3: Draft Using only the findings from the research stage, draft the brief for {{audience}}: a one-sentence summary, the three developments that matter most with why each matters, and the open questions. Quote the evidence behind every claim and never introduce a fact the research stage did not establish. ## Stage 3 of 3: Package Turn the draft into the final deliverable about {{topic}}: a subject line, a short intro, the three developments with their evidence links, and a closing recommendation. Keep the wording the draft stage settled on and flag anything the research stage could not verify.

Inputs

  • Topic{{topic}}

    The subject each weekly brief covers.

    Example: Developer tooling security

  • Audience{{audience}}

    Who reads the brief, in their own words.

    Example: Engineering leads at seed-stage startups

Required MCP capabilities

  • Read approved research sources
  • Write a content draft

Permission boundary

Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.