← Back to library

Run a 500-page docs site as the only technical writer

Devin Logan is the sole technical writer at Fern, which ships about five times a week across nine SDK languages. A Slack-based writing agent turns threads into draft documentation pull requests; Claude Code handles local restructuring and wording across files; chat models help with framing. She reshapes agent drafts she disagrees with and ships around 20,000 lines a month.

  • OutcomeKeep documentation current for a fast-shipping product by sending mechanical updates to agents and spending your own time on structure and judgment.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditDevin Logan
View original
Works with
Claude CodeClaudeCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Route mechanical work through chatTag the writing agent on an internal thread and get a pull request with drafted pages and redirects.
  2. Explore code before writingAsk the code-aware agent how a feature actually behaves.
  3. Restructure locallyUse a local agent to move content, merge pages and trim repetition, checking in a preview.
  4. Workshop wording separatelyUse a chat model for framing launches and blog posts.
  5. 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.

Prompt0 variables
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?
No. It opens pull requests that she reviews and edits.
Why several tools?
Each fits a different job: chat-triggered drafting, local iteration, and writing feedback.

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.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingSkill✓ AI dry run

Make an AI-built screen look designed with the unslop skill

Install Damir Sokolovsky's open unslop skill in Claude Code or Codex, point it at a dashboard, app screen, landing page or even a live URL, approve the short design direction it proposes from your product, and let it fix the screen in nine ordered passes, stopping early if the screen is already good.

Credit: Damir Sokolovsky (@heydamir)

Minutes
MarketingWorkflow✓ AI dry run

Run marketing ops with markdown subagents

A small team of agents that follows a written weekly plan, shares rules and memory through files, and learns from a tracker you can read.

Credit: u/Practical_Dig6095 on r/AskGTM

An afternoon+
MarketingWorkflow✓ AI dry run

Only show research findings whose quotes check out

Build research automations where the model must quote its source and a code step drops any finding whose quote isn't actually on that page.

Credit: u/Fit-Appointment700 on r/n8n

An afternoon+
MarketingWorkflow✓ AI dry run

Swap a part-time research helper for an AI browser

Have a browser assistant gather sources, find people to interview and draft outreach for review while you write in another tab.

Credit: Joanna Stern

Minutes