Write the spec like a regular doc — free to start, no credit card.
the specgit blog
Writing on specs, wikis, research, and docs that live in GitHub, and how product managers, technical writers, UX researchers, and content teams edit them together without learning Git. specgit connects regular document actions like saving, commenting, and publishing to how GitHub works natively, through commits, review threads, and merges. GitHub remains the source of truth, and specgit never keeps a copy of your documents or comments.
Open Obsidian Canvas boards in specgit, edit every note without leaving the board, and review the board and its notes as one set. Plus Grok 4.7, Repo context, and comments that carry across revisions.
Read the postFn First Holdings announces specgit on Microsoft Marketplace. Organizations can now purchase specgit seats through their existing Microsoft agreement.
Read the postYour code and hopefully your specs are now in the repo. User research usually is not. That is how a discovery condition loses to a QBR adoption chart.
Read the postProduct specs go stale because the doc lives in a different tool from the code it describes. What causes the drift, and the setup that keeps specs current.
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