Docs go stale when they live away from the code. Today the spec lives in a doc app, the code in GitHub; engineers get a Slack link, read it once, and build from the ticket — then the doc no longer matches reality.

specgit is the PM-friendly layer on top of GitHub. You write the spec like a regular doc. Engineers review it as a pull request — same flow, same tools, same habits. Every update is a commit. Every discussion is on the record. The doc sits where engineers and AI coding agents already look.

How it works - Saves are commits - Comments are PR review threads - Publish is a merge

Docs never leave your GitHub.

Write without Git or Markdown - Visual editor — no Markdown or Git required - Inline comments and live collaboration - Full history — every change is a commit - Starter templates (product spec, decision record, meeting notes) - Import Word, PowerPoint, Excel, and PDF (via Microsoft’s MarkItDown) - Obsidian Markdown (wiki links, callouts, Mermaid; unknown syntax preserved) - View changes — Word-style redlines against main

GitHub-native review When a repo requires approving reviews, specgit shows what’s needed, authors can request review; reviewers approve or request changes in-app. “Publish when approved” goes live on approval. Works with branch protection and rulesets.

specgit AI (optional) Agent chat, Review, and Triage — text or voice. Only when invoked; every change needs your approval. Never trains models. FreshSpec — early access on request.

Privacy - Documents stay in GitHub; no long-term copy on our side - No analytics, ad tracking, or third-party tracking - Sign-in via the specgit GitHub App — fine-grained, repo-by-repo tokens

Pricing - Free — 1 repo, 5 publishes/month, unlimited collaborators. No credit card. - Pro — $8/seat/month · Pro Plus — $16/seat/month - Viewing and commenting always free.

Try the real editor (no sign-up): https://specgit.com