An open format for writing agent-native software requirements
0 comments · building-ai-tooling, practices, release
- Comments9
0 comments · building-ai-tooling, practices, release
Story details from Lobsters ↗ · linked article on slcr.dev.
An open format for writing agent-native software requirements was first seen on Lobsters · Hottest on Oct 29, 2026. Since then it has appeared in 50 checks on 3 different days. Its best position was #3 of 25, reached on Nov 1, 08:21 UTC. It dropped off the list after Nov 1, 13:21 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Sooo … we spent grillions of dollars and climate credits building out stolen corpuses and infrastructure large enough to run models of natural language that can translate it internally sufficiently well to write programs based on it, so let’s … write a structured data spec for how to talk to it so that our…
I love anything that promotes writing specs. At first I thought writing them in YAML wasn't very exciting for me, but it does enable the structured commands in the CLI like `slcr slice REQ-005`. That is nice. I'll keep it on the radar.
[Author here.] In some sense, it's not that the agent can't sufficiently translate the natural language to the program. An equally big issue is that the human doesn't sufficiently describe the requirements of the program in a persistent way. No matter how good an agent is at coding, if the human doesn't transcribe…
Not at the moment. It was last on the list on Nov 1, 13:21 UTC, after 3 days of trending.
#3 on Lobsters · Hottest, on Nov 1, 08:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Oct 29, 2026 and has been on the list on 3 days (50 checks) since.