Show HN: SpecDeck – Bring coding agent decisions back into the spec

A developer released SpecDeck, an early-stage tool that lets coding agents write implementation decisions back into a project spec as proposed changes via MCP, with humans reviewing and publishing them. SpecDeck models its workflow on git: a published spec is main, drafts are branches, and proposals are pull requests, so teams can maintain specs without touching git directly. The tool is aimed at the problem that, as coding agents produce more code, product-affecting decisions become harder to find.

Writing good specs is hard. You don’t know everything upfront and it’s impossible to write every little detail in the spec. Much of my job as a developer has been to treat specs as intent, and fill out the blanks in the code and use the code reviews as a way to question those decisions. But as coding agents have started to produce much more code, the decisions that actually affect the product are getting harder to find. So I created SpecDeck. It helps everyone on the team write specs and hand them over to developers and their agents through MCP. During implementation, agents write the decisions that matter back as proposed spec changes and leave smaller implementation choices in the code. When the work is done, a person reviews and publish those changes into the spec. The workflow is modeled on git: a published spec is main, drafts are branches, and proposals are pull requests. It should feel familiar to developers, while making it easy for the whole team to work with specs and keep them up to date without touching git. It’s still early and there’s plenty to improve, but I’d love to hear your feedback. Comments URL: https://news.ycombinator.com/item?id=50303157 https://news.ycombinator.com/item?id=50303157 Points: 2 Comments: 0