Home
verso.md
Get started
For Product Teams

Your docs live next
to your code

Stop writing specs in Google Docs that go stale the moment engineers start building. Write PRDs, design specs, and proposals in the same repo as the code, with AI that actually understands the codebase.

PRDs that stay alive

— spec and code land in the same PR
auth-redesign-prd.md
Draft
1# Auth Redesign PRD
2
3## Context
4Current auth uses `src/lib/auth/session.ts`
5which doesn't support OAuth providers.Sarah
6
7## Proposed Changes
8- Add OAuth via `/api/auth/[provider]`
9- Migrate session store → Redis
10- Add `refreshToken` rotation with PKCE flow
11
12## Success Metrics
13- Login drop-off < 5%

Design specs with repo context

AI knows your components. It references actual code, not guesswork.

Release notes & changelogs

Draft in a branch. Review in-editor. Merge with the feature.

RFC & proposal flow

Draft → collaborate async → publish as PR for formal review.

Design system docs

Component docs versioned with the code. Templates keep it consistent.

Ask the codebase, not the engineer

The AI terminal lets PMs interrogate the codebase in plain English. Understand how features work, surface edge cases, and write specs that use the exact variable names, component names, and API routes from the code.

AI Terminalconnected to acme/app
you→How does the auth flow work? What happens when a user logs in?
Login starts in `src/app/login/page.tsx` which calls `signInWithGithub()` from `src/lib/supabase/client.ts`. On callback, `/api/auth/callback/route.ts` exchanges the code for a session and sets `sb-access-token` and `sb-refresh-token` cookies.
you→What edge cases should I cover in the auth PRD?
Based on the current code, watch for: 1. Token refresh race condition: `refreshSession()` has no lock 2. OAuth state mismatch on mobile: `pkce` verifier isn't persisted across redirects 3. No `onAuthStateChange` cleanup in `useEffect`, possible memory leak
you→Write a draft section for the PRD covering these edge cases
Inserting into your doc...
Understand how features workSurface edge cases from codeUse exact variable & component namesGenerate spec sections from code contextExplain API behavior to non-engineersFind undocumented dependencies

From idea to merged PR

01
Write
Draft in verso.md
02
Collaborate
Real-time with your team
03
Review
PR with threaded comments
04
Ship
Docs merge with code

Why verso.md for product?

AI that references real code, not hallucinated endpoints
No copy-paste gap between your doc tool and your code tool
Drafts for async iteration, one-click PR when ready
Templates for PRDs, RFCs, changelogs, component specs

Ready to try it?

Sign in with GitHub and start writing docs that live next to your code.

Get started, it's free