{"slug": "one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor", "title": "One AI Wrote, Another Reviewed: 819 Comments in a Month, and 90% Were Minor", "summary": "A solo product manager for a beauty-salon mobile app built a two-agent review loop in which a separate read-only AI automatically reviews every Backlog ticket write of at least 200 characters, while the writing AI applies fixes. Over October 16 to November 13, 2026, the system logged 291 writes across 87 tickets and ran 175 reviews producing 819 comments, only 74 of them high severity, catching errors such as a deadline listed as \"none\" and a sample count of 48 that was actually 40. The PM kept human execution for production database changes, a split that blocked a faulty delete on November 5 when the AI's pre-check SQL returned zero rows.", "body_md": "TL;DR\n\nI am the only PM on a mobile app for beauty salons, working with offshore engineers. Writing investigation results and spec summaries into Backlog tickets had gradually become the AI's job.\n\nAs the volume grew, small errors started slipping in: broken links, wrong facts. A human re-reading everything does not scale, and I knew I would stop doing it.\n\nOn October 16, after asking for a one-off recheck of an AI-written investigation, I asked for the permanent version instead: whenever the AI posts to Backlog, a review should start automatically, every time.\n\nWhen a ticket is created or its body is updated, and the body is at least 200 characters, a separate review-only AI starts on its own. The reviewer can read but never writes to Backlog. Fixing is done by the AI that wrote the text. The writer and the checker are different agents on purpose.\n\nThe first launch failed: the freshly created agent definition was not loaded into the running session. That day, another agent read the definition file and ran the reviews in its place, and the loop was live by the end of the day.\n\nThe period is October 16 to November 13, 2026. 87 tickets were involved, writes were detected 291 times, and 175 reviews actually ran.\n\nOnly 15 of the 175 reviews came back with nothing to say. The median was 4 comments per review.\n\nOn the very first day, a high-severity comment appeared. In a table listing child tickets, one ticket's deadline was written as \"none\" when it actually had one. Every other deadline in the table was correct, which is exactly why a skim would miss it.\n\nOther real ones: a rollback procedure pointing at the wrong tag, and \"48 samples\" in a write-up when the actual count was 40. Each read naturally as prose. All of them were factual errors.\n\nAnother day, a premise written into a screen-rework ticket contradicted the implementation ticket for the same feature. The writing AI fixed both tickets, and each fix triggered another review.\n\nHigh severity was 74 of 819, under 10%. Low and needs-confirmation together were over 60%. Checking everything with the same effort was the wrong default.\n\nOn October 20 I stopped reviewing comments and kept only ticket creation and body updates, the places where facts get written down.\n\nHonestly, I almost never read the review comments myself. The writing AI fixes its own text in the same session after each review. This was never a human review step. It is a loop where AIs correct each other.\n\nThe other write target was the production database, and the split there is stricter: the AI drafts SQL, a human executes it. Across the whole period, the AI connected to the database zero times.\n\nOn November 5, that split paid off. The pre-check SQL the AI wrote returned 0 rows when a human ran it in production, so the delete was not executed. The AI had misread what a datetime column meant. After changing how the target row was identified, a human ran the delete. Even the completion report got reviewed, and it received a high-severity comment: the SQL quoted in the report differed from the delete SQL posted earlier.\n\nDrafting is where SQL help is fastest. I would like the AI to execute too, but building the safeguards for that is still on my list. For now, execution stays human. That is the honest current state.\n\nAfter a month, four criteria survived.\n\nLetting an AI write is no longer unusual. The difference is in how you verify what it wrote, and where you draw the line between what it may do and what stays with a human.", "url": "https://wpnews.pro/news/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor", "canonical_source": "https://dev.to/mizoko/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor-elm", "published_at": "2026-11-18 12:40:03+00:00", "updated_at": "2026-11-18 12:44:16.872120+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "large-language-models", "ai-safety"], "entities": ["Backlog"], "also_reported_by": [], "takeaway": "Separating a read-only reviewer agent from the writing agent, and triggering review only on ticket creation and body updates, produced 819 comments across 175 reviews in a month, with under 10% high severity.", "recommendation": {"advice": "Split writing and review into separate agents, give the reviewer read-only access, and scope automatic review to the moments facts are written rather than every comment.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor", "markdown": "https://wpnews.pro/news/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor.md", "text": "https://wpnews.pro/news/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor.txt", "jsonld": "https://wpnews.pro/news/one-ai-wrote-another-reviewed-819-comments-in-a-month-and-90-were-minor.jsonld"}}