specgit guides
A Google Docs–style editor for product specs that live in GitHub
Google Docs is great at writing — and terrible at staying true to a shipping product. specgit gives PMs the same easy visual editing, but the document itself is a file in your GitHub repository: saves are commits, comments are pull request threads, and publishing is a merge. The spec lives next to the code it describes.
Why Google Docs fails for specs
The spec lives in Drive, the code lives in GitHub, and the two drift apart from day one. Engineers get a link in Slack, read it once, and build from the ticket; the product moves on and the doc quietly describes a product that no longer exists. There's no review flow engineers actually use, comment threads vanish into "resolved", and sharing is managed in a permissions system your engineering org doesn't control. Meanwhile, AI coding agents working in the repo can't see the doc at all. We wrote up the full mechanism in why product specs go stale.
Saves are commits
Every save in specgit is a real Git commit, attributed to the person who made it. That means full history for free: you can see exactly what changed, when, and by whom, and undo back to any point. No "version history" buried in a menu — the same audit trail your engineers already trust for code.
Comments are pull request threads
Highlight text and comment, just like in Docs — but the thread is a real GitHub pull request review conversation. Engineers reply from GitHub or from specgit, every discussion is on the record next to the change it's about, and nothing lives in a separate silo your team will forget to check.
Publishing is a merge
When the spec is ready, publishing merges it to your base branch — the same flow engineers use to ship code. Repos with branch protection or required reviews work end to end: specgit shows exactly what's needed ("needs 2 approving reviews — 1 so far"), reviewers approve right in specgit, and "Publish when approved" publishes automatically the moment approval lands.
Your docs never leave your repo
specgit reads documents from GitHub when you open them and writes edits back as commits — it keeps no long-term copy. Files stay plain Markdown or HTML, untouched and usable by any other tool. If you ever stop using specgit, everything is already in your repository; there's nothing to export.
Privacy: no analytics, no tracking
specgit runs no product analytics, ad tracking, or third-party tracking scripts. Sign-in goes through the specgit GitHub App with fine-grained, repo-by-repo permissions and short-lived tokens — no separate password, no broad OAuth grant. Read the details on the security and data privacy page.
Move your next spec into the repo
Open any Markdown or HTML doc already in your GitHub — or import a Google Doc — and start writing. Engineers review it in the flow they already use.
Free to start, no credit card. Your docs never leave GitHub.
By continuing, you agree to the Terms of Use and Privacy Policy.
Frequently asked questions
Is specgit a full replacement for Google Docs?
For product specs and docs that should live with the code, yes — you get the same easy visual editing plus real engineering review. For everything else in your Drive (offer letters, spreadsheets, slide decks), keep using Docs. specgit is purpose-built for the documents that shape your product.
Do PMs need to learn Git or Markdown?
No. specgit is a visual editor — you write and format like you would in Google Docs. Saves become commits, comments become pull request threads, and publishing merges your work, all without touching Git commands, Markdown syntax, or GitHub's interface.
Can I move my existing Google Docs into specgit?
Yes. Download a Google Doc as Word (.docx) and upload it to specgit — it's converted to clean Markdown (using Microsoft's open-source MarkItDown) and saved into your repository. PowerPoint, Excel, and PDF files convert the same way.
Does specgit store my documents on its servers?
No. specgit reads documents from GitHub when you open them and saves edits back as commits. Your repository stays the source of truth; specgit keeps no long-term copy, runs no product analytics, and uses no tracking scripts.
Is there a free plan?
Yes. The Free plan covers unlimited collaborators on 1 repository with 5 publishes per month — no credit card required. You sign in with GitHub through the specgit GitHub App, which only reaches the repositories you explicitly grant.