IMO the raw Claude CLI is great for one-off interactive sessions, but as soon as you want repeatable multi-step workflows you’re either copy-pasting prompts forever or hacking your own solution manually. That’s exactly the gap these tools fill.
My take on a solution for this is https://ossature.dev — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.
I use bash scripts. Both Claude and Vibe support all kinds of arguments if you need a prompt to “become a task”. Bash is also deterministic and easy to read and debug.
I did a Show HN[0] a few days back with my CLI agent called cook[1] and for a moment I was ecstatic my tool made it to the front page. haha.
[0]: https://news.ycombinator.com/item?id=47262711 [1]: https://getcook.dev
There is a skill installation option. The skill markdown has 180 lines [1].
My take? I like it. It's concise enough for me to try it out. And I love the webpage.
[1] https://github.com/rjcorwin/cook/blob/main/no-code/SKILL.md
Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in?
IMO the raw Claude CLI is great for one-off interactive sessions, but as soon as you want repeatable multi-step workflows you’re either copy-pasting prompts forever or hacking your own solution manually. That’s exactly the gap these tools fill.
My take on a solution for this is https://ossature.dev — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.
I use bash scripts. Both Claude and Vibe support all kinds of arguments if you need a prompt to “become a task”. Bash is also deterministic and easy to read and debug.
Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does?
As a prerequisite you’d want to understand the purpose of Ralph Wiggum Loops
But in general this is meta to the CLI agent.
So if you were to use the CLI to perform a review of some code. This tool would allow you to loop the output of the code review 5 times onto itself.
Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts.
You could accomplish all of it with claude -p (headless mode).
Admittedly I might be missing a flag or two with claude, but how are multiple loops and comparisons of solutions done with just headless mode?
Via skills.
Indeed.
Where are people finding time for these sort of projects.
claude> "We want to add a title section that shows what page we are currently on, use cook to manage the development process"
* coolers whirring, gpus on fire, tokens flying, investors happy, developer goes for 6th break of the day
How does this handle when Claude needs user input? To choose an option, grant tool permission, clarify questions…
open source alternatives are catching up fast. give it 6 months
i wanna pelt rocks at anthropic