Spec-driven Frameworks

[colinmollenhour]

I recently learned about spec-driven frameworks - such as OpenSpec, Github SpecKit, BMOD, and surely others. I've been playing with OpenSpec and the concept is pretty simple, it installs into your repo more instructions and commands to enforce more structure to your initial planning to get better results at the end. In the case of OpenSpec, it consists of a CLI to init and manage changes, and just three slash-commands to create, kick-off and "archive" the changes.

Even when I write a highly detailed plan for a feature, the agent doesn't do a great job of managing the todo list - it will often completely skip writing any tests by the time it gets to the end even though tests were clearly in the requirements. It also adds lots of placeholder "not yet implemented" code and generally I can see the quality degrading as the context grows from writing a feature in one shot. For example, near the end of the todo list, it will run my existing test suite but not add new ones and say it's all done! OpenSpec seems like an interesting solution to this kind of issue. It's basically a framework of rules that you could enforce yourself, but it's been tuned and curated by a large community in a general way.

All that to say, I'd love to see Crush supporting tools like OpenSpec as they seem to be a major improvement - I believe just about all that is lacking today on the Crush side is support for slash-commands.

[vorticalbox]

according to https://github.com/Fission-AI/OpenSpec?tab=readme-ov-file#native-slash-commands it already supports crush

[kujtimiihoxha]

Hey there, custom commands are in fact supported we just did not document them yet.

Here is some docs we will soon add to main https://github.com/charmbracelet/crush/blob/command-docs/COMMANDS.md

[colinmollenhour]

Great to hear it! I'm using 0.17.0 but don't see a User Commands option.. is this only on main?

[colinmollenhour]

The docs only mention commands being placed in the user's config directory. Will project-level commands be supported as well? I tried "openspec init --tools crush" and it created files at .crush/commands/openspec/*.md in my project.

[vorticalbox]

yes it works with a locally in the project

[colinmollenhour]

Ahh, thanks! I do see the User option now in 0.17.0 after pressing /!

[colinmollenhour]

Closing since this is already fully supported. Thanks @vorticalbox !

[colinmollenhour]

Actually re-opening - Is there a way to provide arguments to the commands?

Without that many commands will not work well.. E.g. for openspec you need to give it the proposal or tell it which change to apply. It is possible to do it without the arguments but it wastes a good 30-60 seconds thinking about why you didn't tell it already..

[dudymas]

The documentation mentioned named arguments. Would those suffice?