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

	▲	isodev 16 minutes ago \| parent [-]
		Compared to a random tool someone vibecoded?

▲

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