I'm trying to get my agentic software specification tool Arbiter to release (UI polish/debugging is so slow :/, browser shenanigans are harder than Rust fr). It's basically a tool that AI agents can use to construct a project specification. The twist to Arbiter is that the specs are structured and validated, and you can compile them to get:

Services with stubbed endpoints, UIs with placeholder components, Dockerfiles/Terraform/K8s infra, E2E tests (via declared flows), Github/Gitlab epics/issues/subissues

It's also got github/gitlab webhook integration, so you can do stuff like trigger agents reactively when events occur on a repo, it includes cloudflare tunnel support so you can set up webhooks even in a local dev environment, and the project generator is fully customizable.

▲

fabmilo 3 days ago | parent [-]

How does it work? is just a documentation specification like spec kit?

	▲	CuriouslyC 3 days ago \| parent [-]
		Nope, it's a structured spec agents construct using a CLI or MCP (you can also interact with the spec using a web UI). It's CUE, and validated against a schema. Instead of taking your conversation and generating a markdown document that agents might (but often don't) respect, the agent populates the spec in the service from your conversation, then when you're done you can use the CLI to automatically generate a bunch of code.