Show HN: Deccy – software engineering as decision management
edawise.com
We built deccy out of frustration from working with coding agents.
Although we love the speed that AI has brought to our work, we also want to have control over what we build. While it's not impossible to keep up with the changes AI makes, it is significantly more difficult when compared to writing code ourselves.
We realised that what we cared about most was not controlling every line of the implementation, but preserving our intent (we especially hated when agents would wrongly guess what we wanted). We iterated through planning and spec-driven methods, but found that both writing our own plans/specifications and reading AI-generated versions was tedious and exhausting.
Eventually, we decided to split the specifications up into the decisions that make them up, and get agents to do the boring work of tracking and bookkeeping. deccy is the first realisation of this idea. We're already working on the next iteration, but we wanted to share the mental model we developed.
There's a long way to go from here, and we'd really love any feedback :)