[vladgur]

Imm overwhelmed with a variety of SDD tools out there.

Github spec kit, spec-kitty, symphony, GSD, this.

How do people decide on the framework other than try them all.

p.s. found this mind-boggling list of them all https://github.com/cameronsjo/spec-compare

[sermakarevich]

I looked at most of those, including kiro and tessl. Was early user of GSD when it was suitable for mid+ size projects. Over time GSD grown into beast which is suitable for huge + size projects only producing gigantic specs and burning too many tokens for most of the tasks. So I decided to created my own, with set of steps I need and specs I want.

After few presentations of sddw to different companies, most important conclusion was that the ssd plugin should be customizable. It should fit the typical size of tasks/features you are working on, specs should fit your requirements, set of steps can be different.

So I created claude code workflow (ccw) which allows to compile custom version of workflow on top of sdd approach: https://github.com/sermakarevich/ccw

After making few presentations of sddw to different companies,

[dostick]

I think any add-on SDD is diluting the context and should be using as much as possible anything that is built-in and not external skill. When Claude (or any other lm) begins to ignore the rules, ask it and it will tell you that having too much in context will make it go bad faster.