---
title: "Comment by netproxy on \"AI Workflow Update\" | Hashnode"
description: "The issue tracker as a prompt repository is a framing I want to borrow. One question though: the stacked PR batch still needed several rounds of review feedback"
url: "https://hashnode.com/posts/2026-10-8-ai-workflow-update/6ac6f8bdb2e680c409ab12c8/comment/6ac81c52feab7f2c88ace446"
---

[Discussion](https://hashnode.com/posts/2026-10-8-ai-workflow-update/6ac6f8bdb2e680c409ab12c8)

Comment [AI Workflow Update](https://hashnode.com/posts/2026-10-8-ai-workflow-update/6ac6f8bdb2e680c409ab12c8)

[netproxy](https://hashnode.com/@argumentmoney8117)

[Oct 8](https://hashnode.com/posts/2026-10-8-ai-workflow-update/6ac6f8bdb2e680c409ab12c8/comment/6ac81c52feab7f2c88ace446)

The issue tracker as a prompt repository is a framing I want to borrow. One question though: the stacked PR batch still needed several rounds of review feedback and CI fixes, so is the real win in parallelizing the mechanical work while the judgment-heavy review part stays serial? The CPU and memory cost of dozens of subagents also sounds worth tracking over time. Thanks for writing it up in detail.
