| ▲ | rc_kas 4 hours ago |
| Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in? |
|
| ▲ | beshrkayali 4 hours ago | parent | next [-] |
| 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. |
| |
| ▲ | je42 2 hours ago | parent | next [-] | | Had a quick look. Stumbled upon the markdown format smd. Was wondering if using front-matter instead of a "custom" encoding for parseble data was considered? | |
| ▲ | isodev 2 hours ago | parent | prev | next [-] | | 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. | | |
| ▲ | Yiin 17 minutes ago | parent [-] | | can you elaborate on "easy to read and debug", because in my experience it is anything but | | |
| |
| ▲ | eloisius 3 hours ago | parent | prev [-] | | Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does? | | |
| ▲ | beshrkayali 11 minutes ago | parent [-] | | Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex. Prompts get copied, deps turn manual, and maintenance of your workflow itself becomes the chore. Ossature swaps that for structured SMDs and optional AMDs. Multiple specs build a clean DAG that drops into an editable plan.toml so everything stays traceable without the mess. Feel free to check the example projects on https://github.com/ossature/ossature-examples |
|
|
|
| ▲ | sghiassy 3 hours ago | parent | prev | next [-] |
| 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. |
| |
| ▲ | exolab 15 minutes ago | parent [-] | | > 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. Claude already does that if you ask nicely. |
|
|
| ▲ | transitorykris 4 hours ago | parent | prev [-] |
| Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts. |
| |
| ▲ | esperent 4 hours ago | parent [-] | | You could accomplish all of it with claude -p (headless mode). | | |
| ▲ | transitorykris 4 hours ago | parent | next [-] | | 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? | | | |
| ▲ | brcmthrowaway 4 hours ago | parent | prev [-] | | Indeed. Where are people finding time for these sort of projects. |
|
|
