# specgit
> specgit lets teams edit GitHub docs without learning Git, from Fn First Holdings LLC. Product teams write, comment on, review, and publish the Markdown and HTML specs and docs stored in GitHub using a simple visual editor, and engineers review them in the pull request flow they already use. GitHub remains the source of truth. Zero Content Retention — specgit never keeps a copy of documents or comments.

Important facts:
- Product category: GitHub-native documentation collaboration and review software.
- Primary users: PMs who work closely with engineers, plus the designers and product leaders who write alongside them — they write specs in the repo, engineers review them like any other change, and nobody has to learn Git or Markdown.
- Core features: visual editing, inline comments, live collaboration, GitHub pull request reviews, direct publish, automatic saving, a redline diff of the draft vs main with selective undo (Show changes, in the Status panel), in-editor merge conflict resolution, cross-branch edit awareness, a Continue working list of unpublished drafts, starter templates for new docs (product spec, backlog tracker, decision record, meeting notes, agent instructions), file rename as a true git rename, uploading Markdown/HTML as-is (.md, .markdown, .html, .htm), and importing existing Word/PowerPoint/Excel/PDF files by converting them to Markdown (via Microsoft's MarkItDown).
- Required approvals: repos protected by branch protection or rulesets work end to end — specgit shows what's blocking a publish ("needs 2 approving reviews — 1 so far"), authors request reviewers from the Status panel, reviewers approve or ask for changes inside specgit under their own GitHub identity, and "Publish when approved" publishes automatically the moment approval lands (GitHub auto-merge).
- Markdown compatibility: Obsidian-flavored Markdown is supported — wiki links and embeds, callouts of any kind (custom titles, fold markers), ==highlights==, footnotes, LaTeX math rendered with KaTeX, YAML frontmatter, task lists, and Mermaid diagrams rendered inline; unrecognized syntax is preserved byte-for-byte on save.
- Obsidian Canvas boards (every plan): .canvas files (JSON Canvas 1.0) open as pan-and-zoom boards in the browser, and New document → Board creates one. Note cards open the note beside the board in the full editor (autosave, comments, properties, Changes); text cards edit in place; cards drag, connect with labeled arrows, group, and take colors; pasted or dropped images become image cards. Lay out a folder turns every note in a vault folder into a card, with each subfolder as its own group. Teammates co-edit a board live, with cursors and a marker on the card each person is editing, and comments attach to cards as GitHub pull request review threads. Saves keep Obsidian's exact file format: an untouched card is written back byte for byte, and a moved card changes one line. A board and the notes on it are reviewed and published together from the board's Status panel, notes first and the board last, each file on its own pull request; each file merged counts as one publish. On phones, cards can be added, moved, edited, and commented on, and a note opens full screen with Back to board; resizing, drawing arrows, and grouping are desktop only. Not supported: drawing, shapes, and embedded web pages.
- AI (specgit AI): runs on xAI's Grok 4.7, with three in-editor modes — Agent chat co-editing, Review (posts inline comment threads), and Triage (works through open comments) — plus voice; AI runs only when invoked and every AI-proposed change requires human approval. Documents can be converted between regular and Obsidian-flavored Markdown from the toolbar.
- Repo context (Pro and Pro Plus): an AI panel setting, off by default, that lets specgit AI read other files in the same repository from GitHub for that request only — Documents (other Markdown and HTML docs) or All files (adds code and config); type @ in the AI panel to point it at a specific file. It isn't included on the Free plan or in the monthly courtesy Review and Triage runs.
- specgit AI on Canvas boards (Pro and Pro Plus): reads the board's cards, groups, and arrow labels in reading order plus the notes on it, and proposes board changes (drawn as ghost cards until applied) and edits across its notes, each approved by a person. On a board it can add, connect, and group cards; it can't delete them.
- Comments across revisions: open review conversations carry onto each new review pull request, anchored to the text they were about; resolved history stays visible by revision, a read-only view ("View in that version") shows the document as it was when a comment was made, and Resolve all closes every open conversation in one step.
- Status panel (every plan): the Status button in the editor's top bar shows where a document's or board's review stands (In progress, In review, Waiting on review, Ready to publish, or Conflicts). Its panel lists the files in the review and what changed, adds reviewers when submitting (GitHub notifies them), publishes, offers Undo right after a submit, can move a submitted review back to a draft until it's published, and abandons a review from its ••• menu (closing the pull request, discarding the draft, and resolving the comments started in that review; open conversations from earlier reviews continue). Ask AI, Status, and Comments open as separate, side-by-side panels that resize and remember their width. Share shows and copies a link to the document or board and a README badge snippet, and links the file and its review on GitHub.
- Repo navigation: repos with more than one folder open as a folder tree beside the folder's contents; Cmd/Ctrl-K or t jumps to any file; filters narrow the list to Has changes, Mine, or HTML; new docs are created in the folder being viewed; and a link to a heading in another doc, including [[Note#Heading]], opens that doc at the heading.
- Getting started: everyone signs in through the specgit GitHub App — fine-grained, repo-by-repo permissions with short-lived tokens, no separate password, no broad OAuth grant. Individuals install it on their account; organizations install once via an admin (members can request it in one click). The repo list shows every repository the user's installations can reach — including org repos accessed through team membership — and users can switch GitHub accounts from the header menu.
- Privacy posture: Zero Content Retention: we never keep a copy of your documents or comments. GitHub remains the source of truth — the only things that ever touch our servers are temporary: live-collaboration state while you edit together, AI processing you explicitly invoke, and feedback you explicitly choose to share. specgit uses content-free product analytics to improve the product — analytics never receive documents, comments, prompts, selections, chat, audio, repo names, filenames, paths, raw URLs, or input text. Outside the EEA, UK, and Switzerland, public measurement is cookieless and unidentified; signed-in events are pseudonymous and can be opted out. In those regions — or when region is unknown — nothing is sent before separate, informed, revocable opt-in. No ad tech, sale, or retargeting. See the Privacy Policy for the processor, retention, and controls. Operational logs are retained up to 30 days.
- Pricing: Free (unlimited collaborators — comments, drafts, and live editing for the whole team — on 1 repository with 5 publishes per month, plus 1 AI Review and 1 AI Triage run per month); Pro $8/seat/month with unlimited repositories and publishing, the full AI co-editor pay-as-you-go, a one-time $10 AI credit in the first month, and 3 AI Review + 3 AI Triage runs included monthly; Pro Plus $16/seat/month adds $10/month of included AI usage per seat and 10% off on-demand AI rates. FreshSpec add-ons for autonomous doc freshness are available via contact for early access: 1 repo / 5 docs, 5 repos / 25 docs, 20 repos / 100 docs, and Custom. Per-seat, billed via Stripe; annual billing saves 20%. Enterprise plans with volume discounts are available via the support form.
- Team billing: seats count editors only (viewing and commenting are always free); org admins buy for the whole organization from billing settings; one subscription can mix Pro and Pro Plus seats; Pro Plus seats are assigned to named GitHub users; active editors are never cut off by seat limits — when a new editor exceeds purchased seats, a prorated seat is added to the subscription automatically (auto-true-up, on by default; admins can opt out, which instead blocks new editors beyond the cap).
- AI metering: usage is measured in dollars at published rates ($2.40/1M input, $0.60/1M cached input, $7.20/1M output tokens, $0.06/minute voice). Beyond included allowances, on-demand usage is off by default until an account admin enables it with a monthly limit; it is billed in arrears, with a full usage dashboard and CSV export. Requests are throttled to 10/minute per person. AI runs only when a user invokes it. Routine AI usage records contain metadata, not content. Separately, a conversation transcript is retained for up to 90 days only when the user explicitly chooses to share it as feedback. xAI's Zero Data Retention is enabled for specgit — xAI does not persist API inputs/outputs and never trains on them; every AI-proposed change requires human approval.

## When to use specgit
Reach for specgit when the job is editing, commenting on, reviewing, or publishing Markdown or HTML that lives in a GitHub repository — or when a product team needs a visual editor whose saves are commits, comments are pull request review threads, and publish is a merge. Start with this file for product facts, then fetch individual pages as `text/markdown`. Authenticated review tools and the MCP server at /api/agent need a GitHub App session; there are no API keys. specgit is the wrong fetch for a model API, a webhook hub, OAuth-app credentials, or GitHub's own REST or GraphQL APIs.

## Developer resources
- [specgit developer resources](https://staging.specgit.com/developers): OpenAPI, MCP, GitHub App auth, markdown negotiation, the /try sandbox, versioning, and the problem+json error model.
- [LLM index](https://staging.specgit.com/llms.txt): Product facts, pricing, and when-to-use guidance. Prefer this over scraping HTML.
- [Full LLM context](https://staging.specgit.com/llms-full.txt): One-file Markdown of the highest-authority public pages.
- [OpenAPI](https://staging.specgit.com/openapi.json): Typed agent API for document review tools, including problem+json errors.
- [Agent auth](https://staging.specgit.com/auth.md): GitHub App sign-in. specgit has no API keys and no password. A session cookie is the credential.
- [MCP server](https://staging.specgit.com/api/agent): Streamable HTTP MCP at /api/agent. Discover the card at /.well-known/mcp.json. tools/call needs the session cookie.
- [Sandbox](https://staging.specgit.com/try): The real editor on a sample document. No account required.
- [Agent skills](https://staging.specgit.com/.well-known/agent-skills/index.json): specgit-docs skill.

## Product
- [Homepage](https://staging.specgit.com/): Plain-language overview of specgit — edit GitHub docs without learning Git — with how it works, feature highlights, and a no-account sample-doc playground at /try.
- [Pricing](https://staging.specgit.com/pricing): Plan comparison (Free, Pro, Pro Plus, FreshSpec) with per-seat monthly and annual pricing, AI usage rates, and billing FAQs.
- [Security and data privacy](https://staging.specgit.com/security): Focused explanation of GitHub as the source of truth, bounded realtime state, content-free product analytics, and user-invoked AI.
- [How specgit works](https://staging.specgit.com/how-it-works): Architecture page — the fine-grained GitHub App's repo-by-repo scopes, conflict-free live co-editing through a real-time collaboration service (temporary state, brokered room tokens), and how every editor action maps to a GitHub primitive (saves are commits, comments are PR threads, publish is a merge).
- [For your IT admin](https://staging.specgit.com/for-your-admin): One-page brief for the admin approving the specgit GitHub App for an organization — exact permissions with justifications, what the installation cannot do, and data posture.
- [Google Docs alternative for product specs](https://staging.specgit.com/google-docs-alternative-product-specs): Comparison guide — why specs drift in Google Docs and how specgit keeps GitHub as the source of truth, where saves are commits, comments are PR threads, and publish is a merge.
- [Docs as code for product managers](https://staging.specgit.com/docs-as-code-for-product-managers): Educational guide — what docs-as-code means for product teams and how specgit gives PMs a visual editor on repo-backed docs without learning Git or Markdown.
- [Obsidian + GitHub collaboration](https://staging.specgit.com/obsidian-github-collaboration): Use-case guide — team editing and pull request review on a repo-backed Obsidian vault, including Canvas boards, with wiki links, callouts, and embeds preserved byte-for-byte.
- [Notion alternatives for team docs and product specs (2026)](https://staging.specgit.com/notion-alternatives): Notion alternatives for docs, specs, and knowledge bases: specgit, Confluence, Google Docs, Coda, Slite, Outline, Obsidian, GitBook, Anytype, AppFlowy.
- [specgit vs GitBook](https://staging.specgit.com/specgit-vs-gitbook): An honest head-to-head on the same criteria: where content lives, how changes get reviewed, what editing feels like for non-developers, publishing, AI, pricing shape, and privacy.
- [Docs as code with non-technical contributors](https://staging.specgit.com/docs-as-code-with-non-technical-contributors): How PMs, designers, and support teammates contribute to a docs-as-code repo without Git: edits become commits, comments become PR threads, publish becomes a merge, and the writer's toolchain stays exactly as it is.

## Blog
- [Blog index](https://staging.specgit.com/blog): Writing on product specs, docs that live in the repo, and GitHub-native collaboration for product teams.
- [Introducing Canvas in specgit](https://staging.specgit.com/blog/introducing-canvas): 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.
- [specgit is now available on Microsoft Marketplace](https://staging.specgit.com/blog/specgit-available-on-microsoft-marketplace): Fn First Holdings announces specgit on Microsoft Marketplace. Organizations can now purchase specgit seats through their existing Microsoft agreement.
- [User insights belong in the repo](https://staging.specgit.com/blog/organic-by-force): Your 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.
- [Why product specs go stale (and what keeps them current)](https://staging.specgit.com/blog/why-product-specs-go-stale): Product 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.
- [Notion vs GitHub for product specs](https://staging.specgit.com/blog/notion-vs-github-for-product-specs): A 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.
- [PRD chatbot vs docs in the repo](https://staging.specgit.com/blog/prd-chatbot-vs-docs-in-the-repo): AI 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.

## Legal
- [Support](https://staging.specgit.com/support): Contact the specgit support team.
- [Privacy Policy](https://staging.specgit.com/privacy): Detailed privacy, data handling, retention, and user rights policy for specgit.
- [Terms of Use](https://staging.specgit.com/terms): Terms governing access to and use of specgit.

## Organization
- [Fn First Holdings LLC](https://fnfirst.com): Company behind specgit.

## Optional
- [Full LLM context](https://staging.specgit.com/llms-full.txt): Curated single-file Markdown of the highest-authority public pages (product, pricing, security, architecture, guides, and blog posts) for agents that prefer one fetch.