When should you use it?
- Features ship faster than docs can follow
- Docs live in a repository
- You are one writer or a very small team
Not for: Docs that need legal sign-off on every line; Teams without code review for documentation
What do you need, and what do you get?
You need
- Docs in a Git repo
- A chat-triggered agent with codebase context
- A local coding agent and preview server
You get
- Draft docs pull requests from chat threads
- Restructured sections across many files
- More time for editorial decisions
How does it work, step by step?
- Route mechanical work through chatTag the writing agent on an internal thread and get a pull request with drafted pages and redirects.
- Explore code before writingAsk the code-aware agent how a feature actually behaves.
- Restructure locallyUse a local agent to move content, merge pages and trim repetition, checking in a preview.
- Workshop wording separatelyUse a chat model for framing launches and blog posts.
- Edit structure you disagree withShe folded a new option into an existing step rather than keeping the agent's separate one.
The prompt
Our own prompt, inspired by Devin Logan and written to work in Claude Code, Claude and Custom agent. Values in lime are placeholders.
Here is a Slack thread describing a new feature: [thread]. Read the relevant code in [repo] to confirm how it behaves. Draft documentation updates as a pull request: change existing pages before adding new ones, add redirects for anything moved, and follow STYLE.md. In the description, list every claim you inferred rather than confirmed in code.
Inspired by Devin Logan: The AI-assisted solo technical writer. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Agent drafts often get structure wrong even when facts are right.
- Context gathering from many tools can pull in stale information.
Our take
Devin Logan's account is a useful look at a realistic division of labor, written by someone doing the job as the lone docs writer at Fern, covering about five weekly releases across nine SDK languages. Routing Slack threads into draft documentation pull requests, using Claude Code for local restructuring across files and chatting for framing, then reshaping drafts she disagrees with, is how she ships around 20,000 lines a month without surrendering ownership. The key behavior is that she still owns structure and pushes back. If you run docs for a fast product, start by routing release-note-sized changes through an agent and measure how much editing each needs. Keep a style guide in the repo so every agent reads the same rules. Explore the code before writing so examples match reality. Separate mechanical updates from conceptual explainers; agents handle the former better. Never publish an agent draft you have not read end to end.
Where the time goes back: Routine updates and file shuffling go to agents, so the writer's hours go to what readers will notice.
FAQ
Does the agent publish docs?
Why several tools?
Source and credit
Inspired by Devin Logan. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- The AI-assisted solo technical writer
- Creator
- Devin Logan
- Published on
- buildwithfern.com
- Original date
- Mar 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.