请问HN：你在使用规范驱动开发吗？
在专业环境中与大型语言模型（LLMs）合作的开发者们，规范驱动开发（Spec Driven Development，简称SDD）真的能成为LLM编码代理的未来方向吗？
在过去几个月里，我努力尝试采用SDD。在试用了SpecKit和GSD后，我最终选择了OpenSpec作为我首选的规范生成器。
然而，我并不准备放弃对LLM生成的实际代码的理解。
为了帮助我保持对生成代码的理解，我尝试了几种不同的方法，比如为更细粒度的功能生成较小的规范，并在每个主要任务块完成后暂停以审查代码。通过“/ospx-apply 运行直到任务3.5完成，然后暂停以进行审查”的方式，我能够审查生成的代码，并在必要时进行修正。但老实说，我面临的主要问题是编码风格和良好的代码规范往往缺失，即使在加载了适当的AGENTS.md和技能的情况下（通常存在多个辅助方法和不一致的命名问题）。
我不禁想知道其他开发者在他们的工作场所是如何做的。SDD真的作为开发者工具包的一部分被使用吗？我是否在对代码保持过多的控制，应该让LLM在规范的范围内自由发挥？还是我应该放弃SDD，寻找其他途径，以确保生成的代码至少能够长期维护？
查看原文
Developers working with LLMs in a professional environment, is Spec Driven Development really the way forward with LLM coding agents?<p>Over the past few months I've really tried to lean into SDD, after trying SpecKit and GSD, I finally settled on OpenSpec as my preferred spec generator.<p>However I'm not quite ready to give up on understanding the actual code that the LLM is producing.<p>To help with maintaining my comprehension of the generated code, I've tried a few different methods, such as generating smaller specs for more granular features, and pausing after each major task block to review the code. Approaching this via "/ospx-apply Run until task 3.5 is complete and then pause for review" gives me the ability to vet the code being produced and make corrections if needed. But honestly, the major issue that I have is that coding style and good code hygiene is often lacking, even with appropriate AGENTS.md and Skills loaded (the usual issues of multiple helper methods, inconsistent naming).<p>I can't help but wonder what developers are doing in their workplaces. Is SDD actually used as part of the developer toolkit? Am I trying to keep too much control over the code and should I just let the LLM be free within the bounds of a spec to guide it? Or should I abandon SDD and look at another path to ensure that code being produced can at least be maintained long term?