Hi Product Hunt! 👋

Code lives in GitHub, and is the source of truth for what a product does today. But the future of the product — the specs, requirements, and decisions — is shaped by PMs, and that work almost always lives somewhere far away from the code because historically GitHub has not been a good document editor and the good document editors have not been designed for GitHub. Instead, Engineers get a link in Slack to a shared document somewhere, read it once, and build from the ticket — six months later the doc describes a product that no longer exists.

PMs are being asked to get closer to the code than ever. So why not put specs and product docs in the same repo as the code itself? Simple: GitHub is great for code and awful for documents.

❌ No visual editing

❌ No real-time multiplayer

❌ Comment and review flows built for engineers

That's why I built specgit. It's the PM-friendly layer on top of GitHub — built for PMs who work closely with engineers, and the designers and product leaders who write alongside them, without giving up anything from Google Docs or Word:

✅ Effortless visual editing — regular or Obsidian Markdown, no Git CLI required

✅ Real-time multiplayer and inline comments

✅ Reviews that are genuine pull requests, in the flow engineering already trusts

✅ specgit AI in the editor — Review, Triage, and Agent chat (text or voice); every change waits for your approval

✅ View changes as Word-style redlines, resolve merge conflicts in the editor

✅ Your documents never leave your GitHub — we keep no copies, run no tracking

Coming soon: FreshSpec, a separate add-on that autonomously keeps selected docs fresh — watching repos for drift and opening pull requests for your team to review.

The free plan covers a real project: your whole team can comment, draft, and edit live with no limits, on 1 repo with 5 publishes/month — no credit card.

Product hunters: use code PRODUCTHUNT at checkout for your first month of Pro free.

I'd love feedback — especially from PMs who've been told "the spec is out of date" or "build it as spec'd", and from engineers who've watched a spec rot in a wiki. I'll be here all day.

Bryan