The agents · Content · example build
Docs keeper
Every release quietly breaks a little of your documentation. This agent reads what changed, drafts the doc updates and the release notes, and flags the support questions your docs almost answer but do not. The gap between what the product does and what the docs say stops growing.
A shift, illustrated
What a morninglooks like.
Docs keeper · illustrative
- 17:20 · release parsed · 3 doc pages need updates
- 17:11 · drafts ready · screenshots flagged for refresh
- 17:02 · 6 tickets this week ask what docs skip · listed
Publish doc updates for v2.4
3 pages · diff view ready
Needs your call
approval-first. nothing ships without you.
The division of labour
It prepares.You decide.
Prepares
- Doc updates drafted from what changed
- Release notes in your voice
- A list of questions the docs fail to answer
Waits for you
- Publishing to the live docs
- Anything about pricing or terms
Runs against: Your repo or changelog, your docs platform, your helpdesk
This page shows a shape we forge, not software waiting on a shelf. Yours starts from your own workflow at the audit and gets its gates set where you put them.
Where it fits
Common homesfor this agent.
Related examples
Concept batch
Turns your performance data and brand voice into concepts and hooks, delivered in batches.
Brand QA
Checks every asset against your brand rules before it ships, so off-brand never goes out by accident.
Listings writer
Writes and maintains product pages and catalog data at volume, in your voice and your structure.