Use cases · Reporting · Weekdays at 9:00 AM

What you shipped becomes posts, held for your yes

The work happens, the posting does not. Launches go unannounced because writing the post is one more task at the worst time, and consistency is the first casualty.

Your Squad teammate watches what you ship: the GitHub releases, the changelog, the closed milestones on the board. Each becomes drafted posts per channel, in the voice your squad's Voice file defines, waiting in the queue as approval tickets.

Nothing publishes without your tap. Edit a draft in chat and it re-drafts instantly; the edit teaches the voice. Quiet weeks get evergreen drafts from your docs and older wins, so the feed never flatlines.

How it runs
01
Connect the sources

The repo, the changelog, the board. Shipped work is the raw material; nothing else prompts a post.

02
Set the voice once

The squad's Voice file holds the rules: tone, words to avoid, how you sign off. Every draft obeys it.

03
Drafts queue as tickets

Each shippable moment gets post drafts per channel. One tap approves; the teammate schedules for the slots that perform.

04
Edits teach the voice

Change a line in the ticket and the redraft is instant. The correction goes to memory, and the next draft starts closer.

05
The rhythm holds

Quiet weeks get evergreen drafts from your docs and best older posts. The queue never runs dry; you still approve every send.

What lands on your desk
A queued draft, waiting for your tap
DRAFT — LinkedIn · from: v2.4 changelog · slot: Tue 9:10 AM

We shipped scheduled exports last night.

The request behind it: 'I rebuild this report every Monday.'
Now the report builds itself and lands in your inbox before
you are up. Small feature, whole mornings back.

Link in the first comment.

[ Approve & schedule ]  [ Edit ]  [ Skip this one ]
What you get
  • Every ship gets announced, in your voice.
  • Nothing publishes without your one-tap yes.
  • Edits become permanent voice corrections.
  • A feed that stays alive through quiet weeks.
Works with
LinkedInXNotion

Your teammate connects through the integrations you approve, works on its own computer with its own browser, and asks you before anything irreversible.

Your first month
Day 0

You connect the repo and the changelog, and fill the Voice file's rules.

Day 1

Yesterday's release becomes three drafts, one per channel. You edit one line; the redraft is instant.

Week 1

The queue holds five drafts. You approve from the phone in a spare minute; the teammate schedules the slots.

Month 1

The feed has not missed a ship in four weeks. Your edits taught the voice; most drafts go out untouched.

Squads also run