Sundae Bar Logo

Internal comms for recurring updates

Turn standups, ticket lists, sprint recaps or a batch of newsletter submissions into the exact internal update a named reader will read and act on.

Internal Comms Desk is a ready-made AI agent on sundae_bar. You launch it in your browser and talk to it in a chat. Nothing to install.

Run the Internal Comms Desk agent · 2,000 credits free, no card needed

What the agent gives you

Turn messy standups, ticket dumps, and sprint recaps into clear internal updates, with tailored versions for your team, partner teams, and leadership. It won't invent an update; if you don't provide facts, it asks for the three things it needs first.

How it works

  1. 1

    Gather the raw material

    Paste the standups, ticket dumps, sprint notes, newsletter submissions or the draft you already have. Include any house style examples you want matched and say who will read it and where it will be posted.

  2. 2

    Name the reader and constraints

    Tell the desk who the reader is, the channel or email it goes to, and anything to omit or soften. On first use it asks one short setup question and remembers your preferences.

  3. 3

    Receive the finished piece

    It returns only the piece you asked for: a team post, a stakeholder email, an exec section, a newsletter plan, or a rewrite in the target voice. For rewrites it also hands over a short Changes list that ties each edit to an anchor example.

  4. 4

    Review and publish

    Check the assumptions line it states when the material is partial, accept the piece or paste the missing fact it asked for. Use the Changes list to explain edits to authors when you need to preserve tone or compliance.

Lab winner skills inside

Each skill won an open challenge, scored by independent validators against a sealed reference set. We are not marking our own homework.

  • Internal Reporting Playbook

    Turns raw working material like standups, ticket dumps and sprint recaps into internal reports people actually read. It works out who needs to hear what, writes each piece at that reader's altitude, and calls project health straight instead of parking everything at yellow.

    Lab score 77 across 249 submissions · Read the challenge brief

  • Newsletter Planning Desk

    Turns a pile of raw updates into a newsletter plan: what leads, what gets a line, what gets cut and why. It decides for a named audience, so the same pool produces a different brief for all-hands than for leadership.

    Lab score 82 across 93 submissions · Read the challenge brief

  • Voice Match Rewriter

    Teaches an agent to rewrite a draft so it sounds like a particular team, product, publication or person. It measures the target voice from a written guide or real sample messages before changing a word, keeps the hedges that carry meaning, stops when the draft's claims conflict with the brief, and returns the rewrite with a short list of changes.

    Lab score 80 across 228 submissions · Read the challenge brief

Proof points

  • Internal Reporting Playbook: Lab score 0.77, 249 submissions, challenge SBC11 (/lab/challenges/sbc11), skill listing: /skill/internal-reporting-playbook
  • Newsletter Planning Desk: Lab score 0.82, 93 submissions, challenge SBC14 (/lab/challenges/sbc14), skill listing: /skill/newsletter-planning-desk
  • Voice Match Rewriter: Lab score 0.80, 228 submissions, challenge SBC13 (/lab/challenges/sbc13), skill listing: /skill/internal-newsletter-content-selector

What the job involves

Recurring internal updates are a craft. The aim is not to summarise everything, but to give the right reader the facts they can act on at the right altitude. Raw inputs you paste, such as standup notes, ticket exports, sprint recaps or a pile of newsletter submissions, rarely arrive organised for a named readership. Doing the job well means reading the batch twice, surfacing the load-bearing facts with owners and dates, and making an explicit health call when the material supports one. It also means honouring constraints: a name to avoid, a framing to keep, or a strict length cap. When the material lacks the minimum to make a reliable call, the correct move is to stop and ask, not to fabricate a plausible-looking update.

What the agent gives back

The Internal Comms Desk turns your pasted material into the finished artifact you named. Request one piece and you get only that piece: a working-channel post for the team, a stakeholder email, an executive summary, a newsletter plan, or a rewrite in the target voice. For rewrites you also receive a concise Changes list that ties each substantive edit to an anchor example. For newsletter requests you get a plan, not drafted copy: the edition, length target, the lead story with its rationale, the must-not-miss slots, the quick updates and the excluded items with reasons. The agent will mark assumptions and gaps when the inputs are partial, and when necessary it asks plainly for the three minimum facts it needs to proceed. Several skills inside this agent won open challenges, scored by independent validators: the Internal Reporting Playbook, the Newsletter Planning Desk, and the Voice Match Rewriter. Each skill encodes the craft rules you expect: judge the reader, mine the batch for load-bearing facts, separate signal from noise, and match voice without changing claims. Links: /skill/internal-reporting-playbook, /skill/newsletter-planning-desk, /skill/internal-newsletter-content-selector.

How to judge the result

A usable result has three checks. First, a clear routing line or header that says who the piece is for and why it ran. Second, owners and dates for any health call, with at least one line of evidence bound to a status colour. Third, no invented particulars: where the material lacked a fact the piece either marks it as an assumption or stops and asks. For rewrites, the Changes list should make every substantive edit defensible by reference to an anchor. For a newsletter plan, judge the output by the slotting rationale and the discard list: the plan must say what opens the edition, what those readers must not miss, and why each exclusion was discarded. If an output fails these checks, paste the missing fact, narrow the readership, or ask the desk to rerun with a specific channel and it will rework to fit.

FAQs

Questions about internal comms for recurring updates