Support writes it. Product and engineering confirm it on the same link.
Help articles, customer notices, and the release notes your team has to explain. One file, then the help center.
The docs you produce now
Help articles and incident notices fail when they ship a step the product no longer has, or a cause you have not confirmed. The people who know are in engineering, product, and legal. They are not in your agent session.
What you can review with Gander
Loomwright
Help-center articles and macros
Product and the engineer who owns the feature read the article. The engineer uses agent connect to move a step under Settings. Read more →
Emberlane
Customer incident notices
The incident commander, comms, and legal share the notice. Someone uses agent connect to remove an unconfirmed cause. Read more →
Loomwright
Release notes and changelogs
Product, support, and marketing comment on one draft. Support uses agent connect to add what admins do after upgrading. Read more →
A week with Gander
You watch a help article for a feature that just shipped, and a customer notice for an outage the same afternoon.
On the article, the PM leaves a human thread about tone. The engineer uses agent connect: "@agent step 3 changed last release, the toggle is under Settings now." The agent updates the step and replies. On the notice, legal uses agent connect to remove a root-cause line you have not confirmed. The article goes to the help center. The notice goes to the status page.
What you need
One person on your team runs an agent that writes markdown to a file on their machine (macOS, Linux, or Windows through WSL) and installs the Gander CLI. That person is the author. Everyone else opens the link in a browser. No install, no agent account.
Agents that fit
Publish the article after engineering has had a thread on it, not after a paste into chat.