Agent templateDocumentation

Technical Writer AI Agent (Template)

Name: Fleet
Author: Fleet

A technical writer agent keeps documentation current with the codebase. It watches for merged PRs that introduce new APIs, configuration options, or user-facing changes, then updates or creates the corresponding documentation.

Documentation quality depends on knowing your audience and your doc system. A role-specific prompt encodes your doc format, the voice and style guide, where different types of docs live, and the threshold for what requires documentation versus inline comments.

What this agent owns

Update API reference documentation when endpoints or parameters change
Write new guide pages for features introduced in recent releases
Review PRs that include user-facing changes and flag missing documentation
Keep changelog entries accurate and consistently formatted
Audit existing docs for accuracy after major refactors

Recommended model: Claude Sonnet

Documentation writing is structured prose work where Sonnet produces clear, accurate output without requiring Opus-level reasoning.

Example tasks

Write API reference docs for a new webhook event type
Update the configuration reference after a new environment variable is added
Write a getting-started guide for a new CLI subcommand
Review a merged PR and produce a changelog entry in the project format

# create an agent from this template, then start it

$ fleet agent create --name technical-writer--vendor claude-code --template <template-name>

$ fleet agent start technical-writer

Find the exact template name with fleet template list.

Related agent roles

Product Manager →API Designer →Backend Developer →

Run this agent in your fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet