Engineering
Agents that generate READMEs, API references, changelogs, release notes and internal SOPs from code and conversations.
27 published use cases
A Slack agent answers enrollment and coursework questions from your Notion handbook, cites the page, and tags staff when it is unsure.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
A CrewAI crew checks 50 competitor pages, changelogs and news sources every week and sends a short brief covering only what changed.
Explore a unique simulation of Theseus the Mouse, created using Claude's capabilities and three.js.
Via Hacker News · rupellohn ↗FACE is a Go-based tool that streamlines project management by integrating coding agents and maintaining versioned documentation.
Via Hacker News · JCKodel ↗A user had Devin update a page listing AI coding CLI tools; it opened a PR in 5 minutes, but a separate task needed much back-and-forth to find all files.
Original post ↗The author built a documentation crawler for their AI agents that pulled 60 pages of clean Markdown in 49 seconds.
Original post ↗A PM has Claude Cowork read completed Linear tickets, pick what matters, draft the update and suggest email or in-app format, replacing about an hour per sprint.
Original post ↗Neon's docs team has Devin create the weekly changelog from a playbook and open or revise doc PRs from GitHub issues, for repetitive work only.
Original post ↗Devin scanned a rearchitected codebase and delivered a new README as a PR with accurate setup and API details, but struggled with design rationale and purpose.
Original post ↗A planning agent that works across Google Calendar, Linear, Gmail, and Google Docs through MCP.
Original post ↗A weekly Hermes cron job checks merged PRs for changes to tool schemas, CLI commands, config options or env variables to flag docs needing updates.
Original post ↗A technical writer uses Devin to explore code before documenting it, plus a Slack writing agent built on Devin, reporting about 20,000 lines of docs per month.
Original post ↗The poster has Claude act as an automation engineer, doing design and research work and finding related docs and indexes for their job.
Original post ↗A developer's custom agent searched forums and review sites, cross-referenced findings, and produced a cited 3,000-word competitor analysis with target users and an outbound playbook.
Original post ↗The author gives agents a skill file and docs so they generate recipe URLs for a recipe viewer, working even in permission-limited agents like ChatGPT web.
Original post ↗A commenter runs a persistent script that watches tasks and uses Cursor to open pull requests, building a documentation summarizer and a data pipeline.
Original post ↗Luke runs several Hermes agents that read Jira tickets, write code, review PRs, track costs, summarize docs and send updates.
Original post ↗A commenter had Codex do fundamental architecture work for their game, reading engine docs and implementing better animation merging.
Original post ↗Devin's docs describe reading a Notion PRD to create Linear tickets, producing implementation plans for a backlog, and posting customer health summaries to Slack.
Original post ↗A PostHog tutorial has Cursor in Agent mode write a Flappy Bird-style game for the DeskHog device from its README and hardware details.
Original post ↗Cowork handles design docs, task queues and playtests while Claude Code writes GDScript and runs Godot and git.
Original post ↗An agent loop reading a revenue dashboard ran 365 cycles, generating 394 interlinked SEO pages and a webhook inspection tool with landing page, docs and drafted outreach.
Original post ↗A toolset and docs let ChatGPT and Claude agents write LDraw source files that become LEGO CAD models, packaged as a dockerized web app.
Original post ↗An MCP server that consults MDN docs, reports browser compatibility, and analyzes your CSS for the agent.
Original post ↗Kent C. Dodds had Cursor's agent look up migration docs, plan and upgrade Remix v2 to React Router v7 and xstate in his site.
Original post ↗User points Codex at the Logseq CLI docs so it can query and summarize journals and tagged job-application and project pages.
Original post ↗They watch for changes such as merged pull requests or updated processes and draft the matching doc edit: a changelog entry, a README section or a revised SOP. A reviewer approves the change, so docs stay current without a separate writing sprint.
Across the 27 published workflows on this page, the most used tools are Claude (6), Devin (5) and Cursor (4). Each use case lists every tool it needs and the role it plays.
Open any use case to see the tools, the step-by-step setup and example prompts you can copy. Start with a beginner workflow, run it on a small batch and review the output before you automate it fully.