Launch Coordination
The feature is done. The launch is the problem. Marketing needs the positioning locked before it can brief the writer. Support needs to know what breaks before customers find out. Docs needs a spec that stopped changing. Sales needs to know what they are allowed to promise. Each of these depends on someone else finishing first, and the tracking lives in a spreadsheet that is accurate for roughly four hours after someone updates it.
Skynet keeps the launch plan tied to the actual work. It reads the tracker, the docs, and the channels, and tells you what is genuinely blocked versus what someone just forgot to tick. Then it drafts the things that are late.
How it works
Lay out the launch plan
Describe the launch and who owns what. The agent builds the checklist across product, engineering, marketing, and support, with the dependencies between them made explicit rather than assumed.
Track against live tools
Status comes from where the work is — the tracker, the doc, the branch — not from someone remembering to update a cell. The checklist reflects reality without anyone maintaining it.
Draft what is owed
Release notes, the support macro, the internal FAQ, the sales one-pager. The agent writes first drafts from the spec and the tickets, so the owner is editing rather than starting from a blank page at 11pm.
Chase the gaps
Three days out, the agent flags what is still open and who owns it, in the channel where that person actually reads things. Polite, specific, and it does not forget.
Build it from a prompt
One instruction turns a launch from a spreadsheet into something that maintains itself.
The benefit is that the PM stops being the routing layer. The chasing, the drafting, and the status reconstruction happen without you, and you spend launch week on the calls that need judgment rather than on asking six people whether they did the thing.