展示HN：使用规范驱动开发方法生成Claude代码工作流程
自2026年2月以来，我一直在所有中型及以上的编码任务中采用规范驱动开发（Spec-Driven Development, SDD）的方法：<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）已在几家公司中进行了介绍，包括谷歌波兰。通过这些对话得出的一个结论是，一些团队也希望将该插件调整为适应他们的特定需求、项目规模，甚至是非编码任务，如市场调研。
因此，我构建了Claude Code Workflow（CCW）。它是一个为Claude Code生成线性规范驱动开发（SDD）工作流插件的生成器。您只需在一个单独的配置文件 configs/<name>.yaml 中定义工作流，CCW会自动重新生成所有命令、安装脚本和插件清单。您只需添加每个工作流步骤所需的指令。
工作流的每个步骤都会生成一个规范工件，且每个后续步骤都能识别之前生成的工件。您在每个步骤后都会清除上下文。一切都是基于SDD的，适用于任何类型的多步骤任务或工作流。
代码库：<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>