基于用户指南的编码代理开发
由于代理现在几乎掌握了所有的编码过程，我一直在思考，什么是人类方面最好的、持久且可审查的真相来源。
我一直在尝试的一种想法是以用户指南驱动开发，先编写用户指南和原型，然后让代理在此基础上进行迭代，直到他们的工作与指南相符。我几乎停止使用单元测试，而是创建用户体验，也就是说，一个没有上下文的代理会逐步阅读指南，并在工作被视为完成之前，尽量逐字遵循它。
我在一些小工具中使用了这种方法，感觉对整个过程的控制感更强。不过说实话，我不确定这种方法能扩展到多大规模。我很好奇大家认为这种方法在哪些方面会出现问题。
查看原文
Since agents now own most, if not all of the coding process, I've been wondering what would be the best durable and reviewable source of truth for the human side to own.<p>One of the ideas I've been experimenting with is user-guide-driven development, where I write a user guide and mockups first, and let the agents iterate from there until they match the guide. I've almost stopped using unit tests and create user-experience instead, i.e. a context-less agent goes through the guide and tries to follow it literally before the work is considered done.<p>I've been using it in small utils, and feel more in control of the process. tbh though, I'm not sure how far this approach can scale. I'm curious where people think this breaks.