Skip to content
SpecifyDocs

First steps

Introduction to Specify

Specify automates developer documentation for small development teams. It connects GitHub code changes to the related docs and prepares proposed updates backed by evidence.

Specify reads code changes, finds the developer docs that need to change, and turns them into proposed updates you can review. Even a small team with no time to write docs by hand can keep developer documentation in step with the code just by connecting a GitHub repository.

There are two main ways to use Specify, and you can combine them depending on your team's needs.

Documentation automationSpecify MCP
What it isA workspace feature that generates developer docs from your GitHub repository and prepares proposed updates as the code changesAn MCP server that lets coding agents such as Claude Code, Codex, and Cursor read the docs and context in your team's workspace
Best forKeeping API, architecture, and onboarding docs in sync with the codeWorking on top of team context without pasting project background into your agent every time
Get startedQuickstartMCP overview

What Specify does

Connects code and docs
Connects GitHub repositories and branches to a document project and generates your first docs from the code.
Proposed updates with evidence
When code changes, finds the affected docs and prepares a proposed update with the reason for the change and a before-and-after view.
Answers from team context
Answers "why was it built this way?" and "where is it?" using your docs, decisions, and code history as evidence.

New document projects start without automatic updates. Every change arrives first as a proposed update with its evidence, and how updates are applied after that follows your project settings and the applicable policy.

Follow these steps to go from creating a workspace to developer docs your whole team uses.

Create a workspace
Sign up, create a workspace, and connect a GitHub repository.
Go to the quickstartCreate a document project
Choose the repository to document, the document types, and an update mode, then generate your first docs.
Read the guideReview proposed updates
Check the evidence and scope of the proposed updates that code changes produce.
See the review flowConnect a coding agent
Let Claude Code or Codex reference your workspace docs directly.
See how to connect

Evidence behind accurate docs

Specify's AI doesn't make up documents from general knowledge. It searches for evidence before it writes.

Workspace RAG
Searches your workspace's docs, uploaded files, and connected sources to answer and write from your team's facts.
Standards library
Searches and cites clauses from standards such as IEC 62304 and ISO 14971, and flags content that has no evidence.
The right model for the task
Choose a lightweight model for search and summaries, and a model that's strong at document work for writing.

Common use cases

  • API and developer docs: Keep endpoints, request schemas, and response fields aligned with the code. See Keep API docs up to date.
  • Onboarding docs: Use your repository structure and run instructions to create docs that get a new teammate to a working setup on their first day. See Generate onboarding docs.
  • Team knowledge search: Get answers grounded in team context without digging through docs or pulling a colleague aside. See Ask AI.

Learn more

Tour the interface
Learn the layout, including the sidebar, tabs, search, and Inbox, with real screenshots.
Security and data
Review data isolation and permission boundaries.
FAQ
Common questions from teams evaluating Specify.