← Back to context Comment by wyre 10 hours ago It's just a bundle of skills and md files...Why does it need to have an entire CLI? 3 comments wyre Reply iamjfu 10 hours ago The CLI is actually useful. It gives the skills a way to deterministically interact with the spec. For example, it can validate the shape without having to spend tokens reading the files. wyre 9 hours ago Compared to including shell scripts with the skills?Not trying to say that it's not useful, but it seems excessive and potentially bloated. etoxin 8 hours ago I use the cli tool outside of the agent session. e.g. `openspec view` to see all the specs and what's pending.
iamjfu 10 hours ago The CLI is actually useful. It gives the skills a way to deterministically interact with the spec. For example, it can validate the shape without having to spend tokens reading the files. wyre 9 hours ago Compared to including shell scripts with the skills?Not trying to say that it's not useful, but it seems excessive and potentially bloated. etoxin 8 hours ago I use the cli tool outside of the agent session. e.g. `openspec view` to see all the specs and what's pending.
wyre 9 hours ago Compared to including shell scripts with the skills?Not trying to say that it's not useful, but it seems excessive and potentially bloated. etoxin 8 hours ago I use the cli tool outside of the agent session. e.g. `openspec view` to see all the specs and what's pending.
etoxin 8 hours ago I use the cli tool outside of the agent session. e.g. `openspec view` to see all the specs and what's pending.
The CLI is actually useful. It gives the skills a way to deterministically interact with the spec. For example, it can validate the shape without having to spend tokens reading the files.
Compared to including shell scripts with the skills?
Not trying to say that it's not useful, but it seems excessive and potentially bloated.
I use the cli tool outside of the agent session. e.g. `openspec view` to see all the specs and what's pending.