3 ms·

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 for

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 https://ossature.dev — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.

eloisius 7mo ago
Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does?
- beshrkayali 7mo ago
  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 https://github.com/ossature/ossature-examples
  - wiseowise 7mo ago
    > Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex. Then just use Python.
    - beshrkayali 7mo ago
      That’s what Ossature is :)
- hrmtst93837 7mo ago
  [flagged]
isodev 7mo ago
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 7mo ago
  can you elaborate on "easy to read and debug", because in my experience it is anything but
  - isodev 7mo ago
    Compared to a random tool someone vibecoded?
    - petcat 7mo ago
      what about a random bash script that somebody vibe coded
je42 7mo ago
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?
- beshrkayali 7mo ago
  Yeah, I did briefly consider front-matter, but ended up with inline @ tags because I thought it kept the entire document feeling like one coherent spec instead of header-data + body, front matter felt like config to me, but this is 0.0.1 so things might change :)

eloisius 7mo ago

Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does?

beshrkayali 7mo ago
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 https://github.com/ossature/ossature-examples
- wiseowise 7mo ago
  > Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex. Then just use Python.
  - beshrkayali 7mo ago
    That’s what Ossature is :)
hrmtst93837 7mo ago
[flagged]

isodev 7mo ago

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 7mo ago
can you elaborate on "easy to read and debug", because in my experience it is anything but
- isodev 7mo ago
  Compared to a random tool someone vibecoded?
  - petcat 7mo ago
    what about a random bash script that somebody vibe coded

je42 7mo ago

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?

beshrkayali 7mo ago
Yeah, I did briefly consider front-matter, but ended up with inline @ tags because I thought it kept the entire document feeling like one coherent spec instead of header-data + body, front matter felt like config to me, but this is 0.0.1 so things might change :)