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?
- Script the recurring choreWrite a reusable playbook for the weekly changelog setup.
- Point it at issuesGive an issue link and ask it to find and update the affected pages in a PR.
- Use it to find, then edit carefullyFor renames, let it locate every mention, but review phrasing rather than accepting find-and-replace.
- Ask for code explanationsWhen support needs to know how a feature works, have it trace the logic and explain.
- 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.
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?
What needed the most cleanup?
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.