← Back to library

Clear a docs backlog with an agent opening PRs

Daniel Price describes on Neon's blog how its documentation team hands Devin steady small jobs. A saved playbook prepares each Friday changelog, and when pointed at a stale docs issue it locates the right pages and opens a pull request. A feature rename showed the limits: it caught almost every mention, but clumsy swaps needed twenty-plus manual fixes.

  • OutcomeHand recurring docs chores, old issues and term renames to an agent that opens pull requests your writers review.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditDaniel Price
View original
Works with
Custom 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?

  • Your docs live in a Git repo
  • A backlog of small docs issues never gets attention
  • Product terms change and references scatter

Not for: Publishing without human editing; Large narrative docs that need a writer's judgment

What do you need, and what do you get?

You need

  • Docs repository access
  • A saved playbook for the weekly changelog
  • Links to open docs issues

You get

  • A changelog scaffold each week
  • PRs that address specific issues
  • A list of every place a term appears

How does it work, step by step?

  1. Script the recurring choreWrite a reusable playbook for the weekly changelog setup.
  2. Point it at issuesGive an issue link and ask it to find and update the affected pages in a PR.
  3. Use it to find, then edit carefullyFor renames, let it locate every mention, but review phrasing rather than accepting find-and-replace.
  4. Ask for code explanationsWhen support needs to know how a feature works, have it trace the logic and explain.
  5. Review every PRWriters keep final say on tone and accuracy.

The prompt

Our own prompt, inspired by Daniel Price and written to work in Custom agent. Values in lime are placeholders.

Prompt0 variables
Docs issue: [link]. Find every page in the docs repo affected by it, list them with the relevant sentences, and propose specific edits. Then open a pull request with those edits. Match our style guide. If the issue involves renaming a term, rewrite each sentence so it reads naturally rather than doing find-and-replace, and flag any sentence you are unsure about in the PR description.

Inspired by Daniel Price: AI Workflows for Docs: Putting Devin to Work. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Literal replacement created doubled words; budget time for cleanup after a rename.
  • An unprompted image insertion was helpful once, but check that any added asset is correct.

Our take

Daniel Price's account is useful precisely because it is a working team's experience rather than a launch demo. The pattern to borrow is using the agent as a finder and first drafter for clerical documentation work: building each Friday's release notes from a stored playbook, and turning an old issue into a pull request that touches the right pages. Those jobs are easy to describe, easy to review and tedious for writers, so the time saved is real. The rename story is the instructive part. Finding every mention of an old feature name across hundreds of pages is exactly what agents do well, but swapping words mechanically produced sentences that read badly, and cleaning them up took more than twenty commits. Ask instead for a list of every mention with a suggested rewrite of each full sentence, then accept or edit them in review. Keep a docs style guide in the repository so drafts start closer to house voice. Review every pull request as a writer, not only for accuracy, since awkward phrasing is what readers notice.

Where the time goes back: Small, steady docs work stops piling up because each item becomes a reviewable PR.

FAQ

What went best?
Small repetitive tasks such as setting up the weekly changelog and working through older issues.
What needed the most cleanup?
The terminology rename, which needed many manual follow-up commits.

Source and credit

Inspired by Daniel Price. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
AI Workflows for Docs: Putting Devin to Work
Creator
Daniel Price
Published on
neon.com
Original date
Jun 23, 2025
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

MarketingWorkflow✓ AI dry run

Cut a talking-head video from its transcript

Transcribe a raw recording locally, have a coding agent decide what to trim by reading the text, render with ffmpeg, and check the result before you publish.

Credit: u/ustype on r/automation

An afternoon+
MarketingWorkflow✓ AI dry run

Feed agents approved templates when making video ads

Give a marketing agent a library of manually approved examples so generated videos and posts follow formats that worked.

Credit: u/tgdn on r/ClaudeAI

An afternoon+
MarketingSkill✓ AI dry run

Let an agent submit your product to directories safely

Use the directory-submissions skill from Corey Haines' marketingskills collection with Claude Code or another agent to check that your product pages are ready, pick the directories that fit, fill a listing kit once, vary the description by directory type, fill each web form with a browser tool, pause for your approval before every submit and log each attempt so nothing is sent twice.

Credit: coreyhaines31

An afternoon+
MarketingWorkflow✓ AI dry run

Ship a vertical clip from research through captions

Turn one topic into a finished vertical video by having an agent run the whole pipeline, research, script, visuals, voiceover and captions, with code-based rendering.

Credit: Vivek Shetye

An afternoon+
MarketingWorkflow✓ AI dry run

Test whether an AI agent can take your survey

Run your own paid survey through a free personal agent before launch, then add checks that catch automated responses.

Credit: u/improvedataquality on r/Marketresearch

Under an hour