the specgit blog
Writing on product specs, docs that live in the repo, and GitHub-native collaboration for product teams. specgit is a GitHub-native docs collaboration app: saves are commits, comments are pull request threads, publish is a merge — and your docs never leave your repo.
Spec drift isn't a discipline problem — it's a location problem. Decisions happen in the repo while the doc lives somewhere else. What changes when the spec sits next to the code, without asking PMs to learn Git.
Read the postA fair comparison of Notion and GitHub as the home for product specs — writing experience, review, history, permissions, AI agents, and tracking — and why the source of truth belongs in the repo.
Read the postAI PRD generators are genuinely good at drafting. But drafting was never the expensive part — the expensive part is where the spec lives afterward and how engineers review it. A fair comparison of the two, and why they solve different problems.
Read the post