Developer docs automation for GitHub
Code is today,documentation is yesterday.
Specify is a developer documentation automation tool for engineering teams. It reads code changes, finds affected docs, and prepares updates for your review.
Connect GitHub. Reduce the recurring work of writing and maintaining developer documentation.
No credit card required · Start with a free personal plan
- Detect changes
- Find affected docs
- Prepare updates
Use Cases
Start with the docs that drift every time code changes.
Connect the documents you use most and review them alongside code changes.
Keep API documentation current
Check endpoint parameters, response fields, and request examples against the code, then review proposed updates.
Generate onboarding documentation
Generate a draft explaining project structure and setup, then add team decisions and access procedures.
Connect GitHub and documentation
Connect repository changes to documentation and review the evidence and scope of proposed updates.
Knowledge-grounded RAG
Write from your team's knowledge, and realign when code changes.
Specify indexes your developer docs and workspace knowledge for RAG and retrieves evidence from it. It writes documents from that evidence, and when code changes it finds the affected documents and prepares updates.
Write documents grounded in what your team already knows
- Dev docs, notes, decisions
- RAG index & search
- New doc with sources
Developer docs and team knowledge in your workspace are indexed for RAG. When a document is created, relevant evidence is retrieved first, and the draft is written with its sources.
- Developer docs and workspace knowledge become one searchable body.
- A source marker that doesn't match a real reference is automatically demoted to plain text.
When code changes, find and fix the affected documents
- GitHub code change
- Detect affected docs
- Update with evidence
Specify reads GitHub code changes symbol by symbol and finds which of the documents your project manages are affected. It prepares an update with the evidence and a before/after, and your team reviews before anything is applied.
- Code is read directly from the repository to understand what changed.
- New projects start with no auto-apply; applying afterwards follows the project settings and policy.
How it works
From connection to update, in four steps.
Keep your GitHub repositories and documentation tools as they are. Just connect them.
Connect
Connect a GitHub repository as a documentation project source and choose the documents to create.
Detect
Read code changes and find the documents they affect.
Propose
Prepare an update with its evidence and a before-and-after view.
Review
New projects start without automatic updates. Later updates follow project settings and the applicable policy.
Pricing
Start solo, then grow into a team.
Start the free personal plan without a credit card.
Free
$0/ month
Organize personal context
- Basic AI usage
- Unlimited documents
- 100MB storage
- Collaboration tools (docs, messaging, issues, code)
No credit card required
Pro
Most Popular$20/ month
Best for individuals with recurring work
- More AI usage than the Free plan
- Unlimited documents
- 1GB storage
- GPT + Claude models
14-day free trial · 2 months free yearly
Team
$40/ seat/month
Best for team collaboration
- 2× Pro AI usage per seat (shared pool)
- Unlimited documents
- 2GB/seat
- GPT + Claude models
14-day free trial · 2 months free yearly
Prices are shown in USD. See the pricing page for local currency prices.
FAQ
Everything you need to know before getting started.
What is Specify?
Specify automates developer documentation for engineering teams. Connect GitHub code changes to the relevant documents and review the supporting context and proposed updates.
How do I connect GitHub to documentation?
Connect a GitHub repository as a documentation project source and choose the documents to create. Check access and source scope, then compare generated documents with the current code. Later updates follow project settings and the applicable policy.
What should I check when updating API documentation?
Check request parameters, response fields, authentication, errors, examples, and compatibility. Compare the evidence and proposed changes with actual API behavior. Your team should supply design intent and migration timelines that are absent from the schema.
What does onboarding document generation help with?
Repository code and configuration support drafts explaining project structure, setup, and key functionality. Add access-request contacts and decisions not recorded in code, then ask a new developer to verify installation, execution, and tests.
Does it change documents automatically?
New projects start without automatic updates. You can review changes and their supporting context. Subsequent updates follow project settings and the applicable policy; low-risk changes may be automatically approved when automation is enabled.
What knowledge are documents grounded in, and how are code changes applied?
Developer docs and team knowledge in your workspace are indexed for RAG, so relevant evidence is retrieved and cited when a document is written. Code is not embedded; it is read directly from the repository. When code changes, Specify reads the GitHub change, finds the affected documents, and prepares an update; applying it follows the project settings and policy, with your team reviewing.
Which documents can I start with?
It works seamlessly for API references, integration guides, Architecture Decision Records (ADRs), onboarding manuals, and release notes.
Do we need to replace our development workflow?
Not at all. Keep your existing GitHub repositories and documentation tools. Specify plugs right into your current flow.
Is our code and documentation secure?
All data runs on enterprise-grade AWS infrastructure with workspace-level isolation. We never train AI models on your code or docs.
How long does setup take?
Connect a GitHub repository, choose your sources and documents, and start generation. Setup and processing time depend on repository size, connection status, and selected documents. Begin with one document you use often.
Can I start for free?
Start with a free personal plan without a credit card. Documents are unlimited, with 100MB storage and basic AI usage. Explore Pro or Max for more personal AI usage, and Team for a shared team workspace.
Start with connected code and documentation.
Connect your GitHub repository and team documents, then review your first document and proposed updates.
No credit card required · Flexible plans from solo free to team workspace
Questions before you start?
support@specify.app