An LLM Agent Plan System Drops DAGs for Linear Checklists
A first-person engineering account from 掘金 · 人工智能 describes a two-month redesign of an LLM Agent Plan system from a dependency-based DAG to a linear checklist. The author attributes the change to verification failures that rolled steps back, inaccurate dependency declarations, difficulty tracking substantive work, and a mismatch between fixed benchmark tasks and dynamically evolving production work. The report concludes that the engine should provide signals while leaving completion judgments to the model, while noting that DAGs may still suit multi-agent or batch workflows with clear dependencies.
The account identifies concrete Plan-engine failure modes—automatic verification rollback, incorrect dependencies, false progress reporting and static scheduling—that can inform how developers structure long-horizon LLM Agent workflows.
2026-10-05·编排与协作·Plan 系统
我们最初把 Plan 设计为 DAG——步骤有依赖关系、可以并行执行。然后花了两个月把它拆回线性清单。这篇文章讲的是这个'退回来'的完整过程:DAG 在理论上为什么诱人、在实践中为什么失败、以及'引擎不该替模型做认知判断'这条原则如何一步步被验证。
"依赖关系"听起来太对了
当你第一次设计 Plan 系统时,DAG(有向无环图)几乎是不假思索的选择。
一个"重构认证模块"的任务可以分解为: