Generate highly-detailed product spec

About 60 to 90 minutes once your spec starts, plus any time waiting in line. We write 10 at a time, and paid specs go first. You'll see your place in the line and watch the writing happen live. We email you when it starts and when it's done, so you can close the tab and go do something else.

Yes. PRD stands for product requirements document, and that is the formal name for what you get. We say spec because it is the word people actually use, but if you or your developer call it a PRD, you are talking about the same file.

One file. It's a markdown document, usually 6,000 to 12,000 lines depending on how big the product is. It covers what you're building, what to build it with, the database tables, every feature in detail, the API, security, the design, and a numbered build order written for an AI agent to follow. You can read it on the site, download it, or send someone a link.

Yes. Our products are planned this way and built this way, and the plan this site was built from is published here for you to read. It is not a demo of the process, it is the process.

It means the plan covers the parts that break real products: the database, the API, login, payments, errors, security, and what order to do it in. A good coding agent gets a long way on that on its own. It does not mean nobody looks at the result. We review what our agents ship, and you should too.

That's the trade. You get the whole thing for free. In return we post it in our public library and it stays there, with a small "Generated at GenerateSpecs.com" line at the bottom. It's how we show people the product is real. If your idea needs to stay quiet, pay for one — paid specs are private.

Yes. Public specs are under a CC BY 4.0 license. Anyone can read it, build it, or sell what they build, as long as they credit GenerateSpecs.com. Paid private specs are yours alone. We don't post them, and we don't claim anything you build from them.

No changes. One payment buys one spec, written once. There are no revision rounds. The questions at the start are where you shape it, so answer them properly. If it breaks on our end, we run it again for free. If we still can't deliver, email us and we'll make it right.

Whatever fits your idea. If you name the tools you want, the spec uses them. If you don't, our agents pick boring, popular technology that a coding agent is least likely to get wrong. Either way, the spec names every choice and says why.

That's the point of the format. Exact database tables, exact API calls, numbered steps, and a clear finish line for each one — written for an agent, not just for a person. The example on this page is the plan this site was built from, so you can see exactly what that looks like. A good coding agent gets a long way on its own. You should still check what it builds.

Two reasons. Most of our users already have a GitHub account. And free specs need a limit — one per account, and the account has to be at least 6 months old. It also means no passwords for us to keep safe.

CRHQ.ai is the company behind this site, and the platform our writing agents run on. It also has an agent called Project Builder that takes a finished spec and builds the product from it. That's step 2.