specgit

About specgit

specgit closes the gap between the people who write specifications and the engineers who review them, without asking either side to move. Non-engineers write and comment in a visual editor with live collaboration and inline comments, no Markdown and no Git; engineers see the result as an ordinary pull request in GitHub, with commits, a diff and a review thread, so the documentation lives in the repository next to the code it describes rather than in a separate SaaS silo. An AI layer sits inside the review — an AI reviewer that flags gaps such as an unnamed owner for a launch-critical task, plus AI triage and an in-editor agent — and it is metered transparently by token with a usage dashboard rather than bundled invisibly. The claim the vendor leads with, and repeats for security reviewers, is Zero Content Retention: GitHub remains the source of truth and specgit never keeps a copy of the documents. Seat accounting is designed around how docs actually get used, with seats covering editors only and unlimited free viewers and commenters, and seats consumed automatically as people edit rather than provisioned in advance. The AI reviewer's example on the homepage is concrete rather than abstract: it flags that a support-runbook owner is unnamed in a launch plan before the pull request merges.

Key Features

Tags