I'm Ryan, I'm building Higherlevel (https://higherlevel.to) so product teams have one place to define and review software changes.
Over the last couple of years, I've been increasingly delegating software implementation to AI coding agents.
However, because it became easier and faster to ship complexity, I realised that it still takes me quite some time to even understand what the software is doing, why it is doing that, or review the changes.
I also don't do traditional code reviews anymore, it's mostly automated but I still want to review the final outcome of the changes (rather than its implementation).
I regularly work on complex B2B applications where a single feature can involve dozen of business rules, edge cases and interactions with existing functionality.
I found myself spending more and more time discovering and explaining requirements to agents, reviewing their output, asking for evdience and trying to establish whether we actually agreed on what correct behaviour looked like.
So I built Higherlevel. The idea is to bring product specifications and proof of work into a single collaborative workspace.
You can: - describe the current behaviour, known limitations and expected changes - define business rules, acceptance scenarios using Given/When/Then - demand evidence in the form of a screenshot, a video, etc - comment directly on the spec, on a specific area of the image or a timestamp of the video - discuss changes, track revisions and approve results with your team
I've written extensively about why I believe in specification driven development (and what it means to me) here https://higherlevel.to/blog/introducing-higherlevel
Higherlevel is currently in beta and built with Elixir, Phoenix LiveView, and PostgreSQL.