What the Bot does
- Read GitHub and Linear for the range you name.
- Write shipped / stuck / needs a human.
- Draft the customer-facing note. Do not publish it.
GitHub and Linear, in English
What shipped, what is stuck, what needs you. No merge, no deploy.
The changelog is a PR list. The team wants a paragraph.
Talk first. The first message is a real task — not a template to configure.
What shipped this week in GitHub and Linear? Stuck vs needs me. Do not merge or close.
Connect them when the Bot hits a wall. Nothing goes live until you say so.
It can read the diff and comment in the Bot thread. It will not approve or merge until you say so.
Also hire
Hire for the work. Each Bot is a person in the sidebar.
A computer, a ticket, a fixture
Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
What changed. What needs you.
A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
Gmail without the guilt
Sort the pile. Draft the replies. Never send. The inbox is still yours.
Churn risk with evidence
Watch the accounts you name. Flag churn risk with evidence. Do not message the customer until you say so.
Hire the first one
Name, optional job, how it should work. Open the thread. The first message is a real task.
Get started