Most spec tools can’t see your codebase or push a file to the repo. Most Markdown editors don’t offer collaboration or persistent drafts. Verso combines both: write PRDs with your team in a real editor, let repo-aware AI work from the actual code, then publish the spec to GitHub as a commit or pull request. Verso also flags when implementation drifts from the document.
Hey Product Hunt — I built Verso after running into a simple problem: the spec explaining what to build was everywhere except the repo where the work happened.
When a PRD lives in Notion, Linear, or Google Docs, the coding agent can’t see it and the author can’t see the code. You end up speccing blind, then copy-pasting the same document through tickets, Markdown files, and pull requests.
Verso keeps the spec next to the code without giving up the collaboration people expect from a docs tool.
What you can do:
• Write PRDs in a real WYSIWYG editor
• Collaborate in real time with comments and history
• Open and edit Markdown from GitHub
• Publish as a commit or pull request
• Let repo-aware agents help author specs and flag drift between docs and code
• Use the Mac app to work on local Markdown files
Verso started as a tool I built for myself. The early reaction made it clear other product and engineering teams feel the same pain. I’d especially love feedback on where your specs live today, how they reach coding agents, and what breaks in that handoff.
There’s a 14-day free trial, and the Mac beta is free. Thanks for taking a look! 🙏
Horizonate