Three skills, one launch calendar

A small team ships every week and launches almost none of it. The thing got built, got merged, and nobody wrote the post. Launches is three skills that keep a launch calendar, three slots a week, and do the writing, so the person on the team only reads, fixes a word, and posts.

They share one calendar in your workspace: three slots a week, each with an owner, a day, and the thing being launched. Launch Ideas reads what the team merged, met about and wrote in the last four weeks and turns each customer-visible thing into a launch candidate, with who it is for and what it still needs (a landing page, a card image, a note). On plan day it fills the open slots with the best fit. Launch Playbook reads every post your team has made, works out what gets read on each account, and checks how each launch did a day and two days after. Post Drafter writes the posts for every planned launch, one per account, the way that account’s playbook says, and files one issue for each thing the launch is missing.

Every post starts as a draft on the launch’s page, and a person posts it. Once the drafts for an account are ones you would post as written, turn on auto-post for that account: give your GBrain that account’s X developer keys, and Post Drafter posts at the slot’s time and says so on the page. It is off for every account until you turn it on, and one word in chat turns it off. A GitHub issue is the other thing filed on its own, and only after you say where issues go.

Each skill is a page of plain instructions in your workspace. Read it, change it in chat (“two launches a week, not three”, “never launch on a Friday”), and it says what it changed.