From PRD to wireframes,
all on one canvas
Your PRD, feature specs, user flows, and wireframes stay connected. Go from writing to screen design without jumping between tools.
Update the acceptance criteria so every delegation is logged.
I suggested the missing criterion.
Pick a feature to open it
2 Approvals & delegation › 2.2
Approval delegation
When an approver is out on PTO or a work trip, they hand approvals to another approver for a set period. When it ends, approvals go back to them automatically.
A spec linked by ID
Break the direction set in your PRD into requirements (R-), features (F-), and specs (S-), all linked by ID. Decisions that span several features go into product policies.
Answer developers before they ask
Fill in nine slots per feature, from preconditions to data, and developers have less to ask mid-build. Anything still undecided stays open as a question.
All the way to screens
Generate user flows from your feature specs, then wireframes from the flow. Your spec carries through to screens without starting over.
Start from structure,
not a blank page
Start from the default PRD structure. See the big picture in graph view, focus on one feature in directory view, and read top to bottom in document view. Edit in any view and the others update too. On Pro and up, pick from five PRD templates or edit one yourself, and AI can suggest the one that fits.
The questions developers ask,
settled up front
Each feature carries nine dev-readiness slots, including preconditions, trigger, exceptions, and permissions. AI drafts them and leaves what's undecided as a question. Answer by picking an option or typing your own.
Map the flow,
then design each screen
Build the screen flow from the features in your spec, with broken connections fixed automatically. Wireframes build on the screens you laid out in your user flow. Pick desktop or mobile, generate only the pages you need, and edit text and buttons right on the canvas. When the spec changes, sync the user flow to match.
See export formatsReview flagged how absent approvers are handled. Let’s decide it.
When an approver is away, route their requests to a delegate.
Added a delegation path to the flow.
Access · setup
Request · track
Approve · manage
Main menu
HomeRequest PTOMy requestsTeam calendarApprovalsMembersSettingsHow to use it
- Enterprise PM
Organize improvements to your live product by requirement and feature ID, so every team is looking at the same structure.
- Dev agency
Agree on scope with the client by requirement and feature, then get the flow and screens signed off in the same spec.
- Solo founder
Work through the slots one at a time until the spec is ready to hand straight to your AI coding tools.
- Developer
Get specs that spell out preconditions, exceptions, and permissions, with open decisions flagged as questions so you know what to ask.
Build one spec that goes from PRD to screens
Get 5,000 credits when you sign up, plus 3,000 credits every day.
Plan up to 3 projects for free.