Use an agent to map code before drafting docs

A technical writer uses Devin to inspect repos and draft docs, then revises the pages locally and with engineers before publishing.

Done with Devin· Intermediate· Mar 2026

What they did
Fern’s only technical writer, Devin Logan, relies on Devin, which already knows the company’s repos, to understand code before she writes about it. She also pings Fern Writer, a Slack agent built on Devin, in an engineering thread; it returns a pull request with draft pages, reordered sections, and redirect changes. After that, she checks out the branch and keeps editing locally with Claude Code.
How it went
She says the workflow produces about 20,000 new lines of documentation each month across roughly 500 pages. Every page still gets her review and often substantial rewriting, and the first draft sometimes misses the right structure or leaves out a changelog entry. In one authentication-docs rewrite, an engineer had to step in because the framing was off, which led to a larger restructure.
Tips
Treat the agent’s draft as a starting point, not a final pass. Keep a human reviewer in the loop for structure, change logs, and any conceptual calls that could affect how the feature is explained.

Try it yourself with Devin

Look through [path or module] and help me draft documentation for [feature or API] for [audience]. Explain what it does, how someone should use or set it up, the key functions or endpoints, and any gotchas. Flag anything that looks uncertain or incomplete. Draft the page in [format or location], then stop and show me the draft before you make, send, submit, delete, or merge anything.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on buildwithfern.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.