What it does
Turns a feature that is about to ship into the set of documents and tasks a launch actually needs, in one pass instead of five separate scrambles. The positioning one-pager, the messaging that sales and support will both use, the FAQ that answers what customers will genuinely ask, and the dated launch checklist with owners on the board. It starts from what the feature does, read from the epic and the spec rather than from a marketing brief written about it. Positioning that drifts from what shipped is the standard launch failure: sales promises the roadmap version, support answers for the shipped version, and the gap arrives as churn a quarter later. One message, several audiences. The customer FAQ, the sales talk track, and the support macro all descend from the same positioning, so the three teams say compatible things. Where they must differ — sales can talk about what is coming, support cannot — the kit says so explicitly. Everything is drafted for review. It writes pages and tasks; it never announces anything to anyone.
Example prompts
- We're launching ABC-100 in three weeks. Build the kit.
- What was in the epic that didn't actually ship? I don't want sales promising it.
- Write the customer FAQ — including the awkward questions about pricing and migration.
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 1 credential (1 required) to connect. See setup
