Skip to the tool

Write a Developer-Ready PRD

An AI PRD generator for your first build: the first proof, up to five user stories with testable criteria, and what stays out.

Project Scope4 questions

Who has the problem, and what you'd build. E.g. a meal planner for couples on different diets.

The part a first user comes back for. E.g. clients book a slot and pay a deposit.

How much time will you give the first version?

Fixed time, flexible scope: the slice fits the time.

A feature or a constraint. Empty is fine.

Your scope appears here, weak points named. Free, no sign-up. AI can make mistakes: check before you act.

How It Works

1

Describe Your Idea

One sentence: who has the problem, and what you'd build.

2

Name the Core and the Time

The one thing it must do first, the time you'll give it, and any must-have.

3

Get Your Scope

The first proof, up to five stories and what stays out. Copy as Markdown or download the PDF.

Where Project Scope Sits in Discovery

What goes in the first build? Project Scope turns your idea into user stories with acceptance criteria, and names what stays out.

Use this when: You want the first build pinned down before a developer or AI writes code.

Who it's for: Founders and product managers handing off a first build.

A Wish Is Not a Requirement

"User can manage their profile" leaves a developer guessing. Every story here gets testable acceptance criteria, or it stays out.

Scope Creep Is Cheapest to Fix in the PRD

Once code exists, every cut feels like a loss. In the PRD it costs one line. Time stays fixed and scope flexes. Each cut says why, and any simpler version that ships instead.

Drops Into Cursor or Claude Code Unchanged

The PRD comes out as Markdown with stable section heads. Paste it into Cursor's chat or a Claude Code session. Each story keeps its acceptance criteria.

Frequently Asked Questions

A product requirements document: a written spec of what software does, who it's for and what "done" means. This tool drafts one with AI from your answers.

Start with the one thing it must do first. Write user stories with testable acceptance criteria. Name each cut and the simpler version. Fix the time; let scope flex.

A first draft, yes. This one works only from what you tell it and searches nothing. Read the PRD before a developer or coding agent builds from it.

As Markdown with stable section heads, each user story with its acceptance criteria. This tool writes it that way: paste it into a Claude Code session or Cursor's chat.

Real-time, roles and permissions, search with filters, file uploads and multi-tenancy. Founders underestimate them. Each gets flagged or cut to a simpler first version, such as email before real-time.

Not by us. Your answers go to the AI for the run, then live only in this tab; a reload clears them. Download the PDF or JSON to keep the result.

Where To Next

Next discovery step:Build Cost

Principles behind it:Scope Shaping, Appetite, Not Estimates

When you're ready to build:MVP in 6 WeeksPWA in 6 Weeks

Built & Maintained by Varstatt

Varstatt is a one-person product studio run by Jurij Tokarski, product engineer since 2011. These tools are free and open — no signup, no catch.