The post is written before the feature is announced

A launch is on the calendar for Wednesday and on Tuesday night nobody has written anything. This reads each planned launch page, the playbook for each account, and the thing itself, and leaves a draft in every slot on the page: the founder’s post, the company’s post, the LinkedIn post, and the short note for the site. After the launch posts, it drafts the reshares for everyone else on the team. A person reads, fixes a word, and posts.

What it does

• Writes one draft per account for each launch the calendar has planned, into the fixed slots on the launch page, and fills them in place when the page changes.
• Settles every draft against that account’s playbook from Launch Outlets: length, link placement, opening, and says in one line which rules it followed.
• Drafts the short note for the site when the launch has none, so the post has somewhere to link.
• After a launch posts, drafts the reshare for each teammate’s account.
• Files one issue per thing the launch is missing (landing page, card image, note), checked against what is already filed, in the tracker you named.
• Says in the launch page which slot the launch has, whose it is and which day.

The reveal

You open the Wednesday launch page at nine and the eight slots are full: the founder’s post under a hundred words with the link in a reply, the company’s post, the LinkedIn post with the longer story, the note. One line under each says which rules it followed. Two issues are filed: the card image and the landing page. You fix one word and hand the founder their post.

Configuration

• The accounts: from Launch Playbook. Each gets a slot on every page.
• Where issues go: the GitHub repository for the missing pieces.
• Voice: each account’s playbook, and anything a person says in chat (“the company account never uses exclamation marks”).
• Auto-post: off for every account. Turn it on for one account once you’d post its drafts as written: give your GBrain that account’s X developer keys, and it posts at the slot’s time.
• How often: when you ask, or every morning after the playbook runs, if an available scheduler can run the work and you approve it.

What it doesn’t do

• It doesn’t post for an account you haven’t turned auto-post on for. Those drafts wait on the launch page for a person.
• It doesn’t write for an account with no playbook from fewer than ten posts; it writes plainly and says so.
• It doesn’t skip a launch with no landing page. It drafts the note and links to that.
• It doesn’t file more than a handful of issues a run, and never one that is already filed.

Triggers

Runs when you ask (“draft the posts”, “write the CLI launch”, “draft the reshares”). Daily drafting needs a verified scheduler and your approval; otherwise it runs one bounded pass now and saves where it got to.