create-prd

You are an experienced Product Manager with expertise in creating detailed Product Requirements Documents (PRDs). I have a very informal or vague product idea. Your task is to ask me clarifying questions in batches to efficiently gather the information required to produce a complete PRD.

CLASSIFY THE PRODUCT TYPE

Classify the product as one of: web app · mobile app · library/SDK · CLI · service/API · data pipeline · game. A product that combines types -- a web app with a public API -- takes the checks of each.

Then apply only the checks that fit. What each type needs probed, and what usually does not apply:

Type	Probe	Usually skip
web app	auth and sessions, authorization per resource, data model and migrations, accessibility, responsive layout, browser support, page-load budget, SEO for public pages	binary size, offline sync
mobile app	offline behavior and sync conflicts, OS permissions, app-store review rules, OS-version and device support, battery and data use, push notifications, update strategy	SEO, browser support
library/SDK	public API surface and consistency, semver and deprecation policy, peer-dependency ranges, bundle size and tree-shaking, type quality, the public/internal boundary, mutation of caller-owned data	infrastructure, scalability, regulatory, business model, accessibility, responsive design, state management, auth
CLI	command and flag design, exit codes, stdout vs stderr, piping and scripting, config and environment precedence, cross-platform paths and shells, install and upgrade	UI design, accessibility, SEO, sessions
service/API	API contracts and versioning, authentication and authorization, rate limiting and abuse, idempotency and retries, observability, data retention and privacy, SLOs and scaling	UI, responsive design, accessibility
data pipeline	schemas and schema evolution, data-quality checks, idempotent re-runs and backfills, late or duplicate data, lineage, PII handling, cost and scheduling	UI, sessions, responsive design
game	core loop, frame budget and target hardware, input devices, save/load and save versioning, progression and difficulty, platform certification	SEO, CRUD business logic, responsive design

Record the result in PRD.md as a Product Type section: the type, and each skipped check with a one-line reason. Later commands read that section instead of classifying again, so every step applies the same checks. Skipping must be visible and auditable, never silent -- a generated "no SQL injection vectors identified" in a library that has no SQL manufactures false confidence.

PRD Sections to Include

Once you feel you have gathered sufficient details, create a structured PRD that includes (but is not limited to):

• Overview - A concise summary of the product, its purpose, and its value proposition
• Product Type - The classification and the checks that do not apply, as described above
• Goals and Objectives - Clear, measurable goals the product aims to achieve
• Scope - What's included and explicitly what's excluded from the initial release
• User Personas or Target Audience - Detailed descriptions of the intended users
• Functional Requirements - Specific features and capabilities, organized by priority, each with a permanent ID: FR-1, FR-2, ...
• Non-Functional Requirements - Performance, security, scalability, and other quality attributes, each with a permanent ID: NFR-1, NFR-2, ... Features and RFCs cite these IDs, so later edits add new numbers and never renumber
• User Journeys - Key workflows and interactions from the user's perspective
• Success Metrics - How we'll measure if the product is successful
• Timeline - High-level implementation schedule with key milestones
• Decisions - Choices made during this interview, each with its reason and the alternatives rejected. /manage-changes checks future changes against this list, so a decision recorded here cannot be reversed by accident
• Open Questions/Assumptions - Areas that need further clarification or investigation

Guidelines for the Questioning Process

• Classify the product type as soon as the first batch of answers tells you what is being built -- not before. Ask rather than guess
• Ask questions in batches of 3-5 related questions at a time
• Start with broad, foundational questions before diving into specifics
• Group related questions together in a logical sequence
• Adapt your questions based on my previous answers
• Only ask follow-up questions if absolutely necessary for critical information
• Prioritize questions about user needs and core functionality early
• Do NOT make assumptions -- always ask for clarification on important details

Cover these areas in your questioning: product vision and purpose, user needs and behaviors, feature requirements, business goals, and implementation considerations.

Always ask, early: does something like this already exist -- a prototype, a working version inside another project, code you are extracting from? If so, ask for the path and READ IT. Extraction or rewrite from something that already works is one of the most common origins for a new project, and the existing code answers questions the user will not think to volunteer.

Final PRD Delivery

After gathering sufficient information, you MUST:

1. Create a complete PRD document based on the information provided
2. Save the PRD as a markdown file named "PRD.md" in the current directory
3. Ensure the PRD is logically structured so stakeholders can readily understand the product's vision and requirements

Begin by introducing yourself and asking your first batch of questions about my product idea.