Show HN: 使用规范驱动开发方法生成 Claude 代码工作流程
2 分•作者: sermakarevich•大约 1 个月前
自 2026 年 2 月以来，我一直在使用规范驱动开发 (Spec-Driven Development) 方法来完成所有中等规模以上的编码任务：<a href="https://news.ycombinator.com/item?id=48231575">https://news.ycombinator.com/item?id=48231575</a>。开发我自己的插件（sddw - 规范驱动开发工作流程 <a href="https://github.com/sermakarevich/sddw/" rel="nofollow">https://github.com/sermakarevich/sddw/</a>）的原因之一是希望根据我的特定需求以及我构建的功能的典型规模进行调整。从那时起，这种方法 (sddw) 已在几家公司（包括 Google 波兰）进行了展示。从这些讨论中得出的结论之一是，一些团队也希望根据他们的特定需求、项目规模，甚至是非编码任务（如市场调研）来调整该插件。<p>因此，我构建了 Claude Code Workflow (CCW)。它是一个为 Claude Code 生成线性规范驱动开发 (SDD) 工作流程插件的工具。您只需在一个 configs/<name>.yaml 文件中定义一个工作流程，CCW 就会自动重新生成所有命令、安装脚本和插件清单。您只需要添加工作流程每个步骤所需的指令。
工作流程的每个步骤都会生成一个规范工件，并且每个后续步骤都知道之前生成的工件。您在每个步骤之后都会清除上下文。一切都基于 SDD，适用于任何类型多步骤任务或工作流程。<p>代码库：<a href="https://github.com/sermakarevich/ccw" rel="nofollow">https://github.com/sermakarevich/ccw</a>
查看原文
I have been using a Spec-Driven Development approach for all mid+ size coding tasks since Feb 2026: <a href="https://news.ycombinator.com/item?id=48231575">https://news.ycombinator.com/item?id=48231575</a>. One of the reasons for developing my own plugin (sddw - spec driven development workflow <a href="https://github.com/sermakarevich/sddw/" rel="nofollow">https://github.com/sermakarevich/sddw/</a>) was to adjust it to my specific needs and the typical size of the features I build. Since then, this approach (sddw) has been presented at a few companies, including Google Poland. One of the conclusions from these conversations was that some teams would also like to adapt the plugin to their specific needs, the size of their projects, and even to non-coding tasks such as marketing research.<p>So I built Claude Code Workflow (CCW). It's a generator for linear Spec-Driven Development (SDD) workflow plugins for Claude Code. You define a workflow in a single configs/<name>.yaml file, and CCW regenerates all commands, install scripts, and plugin manifests automatically. You just need to add the instructions required for each step of your workflow.
Every step of the workflow produces a spec artifact, and every subsequent step is aware of the artifacts produced previously. You /clear your context after each step. Everything is SDD-based and works for any kind of multi-step task or workflow.<p>Repo: <a href="https://github.com/sermakarevich/ccw" rel="nofollow">https://github.com/sermakarevich/ccw</a>