PRDs, roadmaps, and user stories — AI-generated PM artifacts
Product Management Framework encodes senior PM and product strategy expertise into prompt sequences that generate complete product development artifacts. From PRDs that engineering teams actually read to launch checklists that nothing slips through, every prompt produces PM work that ships great products.
Full Access Unlocked
All 48 prompts · All 5 modules
"The PRD generator produces documents that engineering actually reads. The acceptance criteria prompt..."
Sasha M. · Senior PM
Need expert implementation?
Hire an OrchestratorConnect with a certified Prompt.Doctor Orchestrator to deploy this framework for you.
No coding required. You will use ChatGPT or Claude as your AI tool. Follow these steps in order — do not skip ahead.
Purchase & download the framework
Click the buy button on this page. After checkout, go to the and hit Download .zip. Unzip it — you'll get a .md file (the full framework) and a .pdf (easy to read reference). Keep both open.
Open your project — new or existing
This dashboard is designed to integrate into any existing project or be built as a standalone app. If you already have a site in Airo (or Cursor, Bolt, etc.), open that project. If you're starting fresh, create a new project. The Orchestrator Prompt handles both cases — it scans what's already there and adds only what's missing.
Paste the Orchestrator Prompt into your builder's chat
Open the on this page. Copy the Orchestrator Prompt and paste it into your AI builder's chat. It will scaffold the full admin system — secure login, email marketing module, booking engine, and CMS — on top of your existing codebase. This takes 2–5 minutes.
Add your API keys as secrets
Critical — Novice UsersIn your builder, go to Settings → Secrets and add the keys your app needs. For this framework: STRIPE_SECRET_KEY (for booking payments — get it from your Stripe dashboard), ANTHROPIC_API_KEY (for AI-assisted content — get it from console.anthropic.com), and DATABASE_URL (your MySQL connection string). No key is needed for the admin login, CMS, or email modules — those run on your existing infrastructure.
Don't have a MySQL server?
You can purchase a shared hosting plan with cPanel and MySQL at host.esgwon.dev. Once your account is set up, follow the step-by-step guide to create your database and connect it to your AI website builder.
How to set up cPanel MySQL & connect to your AI website →Need help with Stripe?
Get your STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY from your Stripe dashboard. The guide covers test keys, webhook setup, and going live.
Need help with Anthropic?
Get your ANTHROPIC_API_KEY from console.anthropic.com. The guide covers model selection, cost management, and troubleshooting.
Prompting Airo after setup — always name the file
When asking Airo to add tables, columns, or features to the admin dashboard, always include src/server/lib/admin-db.ts in your prompt. Without it, Airo may target the wrong database. Example: "Add a bookings table in the admin database (src/server/lib/admin-db.ts) — do not touch any other database connection in this project."
Run the framework prompts inside your live app
Your app is now running in the builder's preview panel. Open the on this page, copy each prompt one at a time, and paste it into your builder's chat. Replace every [BRACKET] with your real data before sending. Work through the stages in order — each stage output feeds the next.
Test end-to-end, then publish or hand off to your client
Walk through the admin as a real user: log in, create a booking, send a test email campaign, update a CMS image, and run the Safe-to-Publish gate. Once everything passes, click Publish in your builder. Because this is a white-label dashboard, your client accesses it at /admin on their own domain — no Prompt.Doctor branding, no third-party login required.
5 modules · 48 prompts · 7 workflow stages
PRD System
Generate complete Product Requirements Documents: problem statement, user personas, solution overview, functional requirements, non-functional requirements, success metrics, and open questions.
9 promptsUser Story Framework
Epic definition, user story generation (As a... I want... So that...), acceptance criteria (Given/When/Then), and story point estimation guidance.
9 promptsPrioritization System
RICE scoring prompts, MoSCoW analysis, opportunity scoring framework, and backlog grooming session facilitation guide.
8 promptsSprint & Planning System
Sprint goal definition, capacity planning, sprint commitment review, daily standup prompts, and retrospective facilitation.
10 promptsCommunication & Launch
Stakeholder update templates (weekly/monthly/board), feature announcement copy, launch checklist, and post-launch review framework.
12 promptsWrite a Product Requirements Document for [FEATURE NAME] for [PRODUCT NAME]. Context: [DESCRIBE THE PROBLEM THIS SOLVES]. Include: (1) Problem Statement (what user pain are we solving, with evidence), (2) Goals and Success Metrics (3 measurable outcomes), (3) Non-Goals (what this explicitly does NOT include), (4) User Personas affected (who benefits and how), (5) Functional Requirements (numbered list — what the system must do), (6) Non-Functional Requirements (performance, security, accessibility), (7) UX/Design Requirements (key flows, edge cases), (8) Open Questions (what needs to be decided before build), (9) Dependencies (what must be true for this to ship). Be specific — avoid vague requirements like "should be fast".
Generate a complete user story map for the [FEATURE/EPIC] feature of [PRODUCT NAME]. User: [DESCRIBE USER]. Goal: [WHAT THEY'RE TRYING TO ACCOMPLISH]. Create: (1) Epic definition (the big goal), (2) 5-8 user stories in "As a [user], I want [action], so that [outcome]" format, (3) For each story: 3 acceptance criteria in Given/When/Then format, (4) Story point estimate (1/2/3/5/8) with reasoning, (5) Edge cases to handle, (6) Definition of Done checklist. Prioritize stories by user value — mark which are MVP vs. nice-to-have.
Apply RICE prioritization scoring to the following feature backlog for [PRODUCT NAME]. Features: [LIST FEATURES]. For each feature, estimate: Reach (how many users affected per quarter), Impact (0.25/0.5/1/2/3 scale — effect on key metric), Confidence (% — how sure are we about estimates), Effort (person-weeks). Calculate RICE score = (Reach × Impact × Confidence) / Effort. Present as a ranked table. Flag any features where confidence is below 50% and explain what information would increase confidence. Recommend the top 3 to prioritize for the next sprint.
system
9 prompts
prompts
9 prompts
workflow
8 prompts
architecture
10 prompts
templates
12 prompts
"The PRD generator produces documents that engineering actually reads. The acceptance criteria prompts alone have reduced our back-and-forth by 60%."
Sasha M.
Senior PM
"As a non-PM founder, this framework gave me the structure I was missing. Our sprint velocity doubled once we had proper user stories."
Ryan C.
Founder/PM
All 48 prompts across 5 modules are unlocked for your account.
Lifetime access