Reverse-engineer a spec from what you built with AI

The document you skipped

The AI-coding wave mints a specific kind of founder: someone with a working product and no documentation. It runs — but you can't onboard a collaborator, you can't see what's missing, and you can't plan the next phase, because the spec that would tell you all that was never written.

Working backward by hand is tedious and error-prone. Most people just don't, and the product stays a black box even to the person who shipped it.

From built product to as-built spec

Reverse Spec starts from a capability map of your product — its actors, data, routes, and screens — which you generate locally so your source never leaves your machine. From that, it reconstructs how the product actually works as a swimlane flow, finds the gaps versus a complete product of its kind, recommends features and UX improvements drawn from comparable platforms, writes the user stories your product implies, and assembles an as-built PRD.

It's the document you'd have written first, written now from reality instead of assumptions.

Why this is the rare lane

Plenty of tools help you write a spec before you build. Almost nothing helps you recover one after. As more products get built by AI without a plan, “document and find the holes in what I already shipped” becomes a real, unmet job — and the highest-value backlog you have is usually the gaps you shipped past.