AI coding agents already read your repo. Cursor, Claude Code, Copilot. They all index your files for context. The question isn't whether AI will read your repo. It's whether it'll find specs, or nothing.
The only difference is whether your repo has .md files with real specs.
CLAUDE.md, AGENTS.md, architecture docs, PRDs: write them collaboratively in verso.md, and every AI tool that touches your repo gets the full picture.
Docs and code evolve together. AI keeps both in sync.
When your specs are .md files in the repo, talking to AI becomes trivially simple. No copy-pasting. No context windows. Just point at the file.
The more context you put in your repo, the smarter every AI tool becomes.
Write agent instructions with real-time collab. They're immediately available to every AI tool that reads your repo.
"Build the auth flow described in docs/auth-prd.md". A well-written spec IS the prompt. No copy-pasting into chat windows.
Same getting-started guide, same architecture docs, same conventions file. AI reads them all, just like a new hire would.
Document what NOT to do. AI agents read your ADRs and know why you chose Redis over Kafka. They won't suggest Kafka.
AI reads the spec → generates code → you update the spec in the same PR. Docs and code never drift apart.
PRs contain the spec change AND the code change. Reviewers see the full story, not just a diff.
verso.md is the editor that makes this effortless.
Sign in with GitHub and start writing docs that live next to your code.
Get started, it's free