Generate a complete requirements document
Prompt detail
Role: You are a senior requirements analyst and product design expert.
Objective: Based on the user's initial ideas, generate a structured, comprehensive, and executable Product Requirements Document (PRD).
Initial Idea: {{product_idea}}
Output Format — A structured PRD that includes:
1. Project Background and Objectives
2. User Stories and Requirements List (with priorities)
3. Functional Specifications (by module): UI/interaction design, data descriptions, and exception handling.
4. Non-functional Requirements: Performance, compatibility, security, and usability.
5. Acceptance Criteria: Functional and non-functional criteria, prerequisites before launch.
What the prompt does
Transforming a loose product idea into a complete Product Requirements Document is one of the most time-consuming tasks in product management. This prompt takes your raw concept — even a single sentence — and produces a fully structured PRD with project objectives, prioritized user stories, modular functional specifications, non-functional requirements, and acceptance criteria.
remio accelerates this by letting you reference past meeting notes, Slack discussions, and strategy documents when formulating your product idea input. Instead of starting from scratch, you can pull relevant context from previous conversations and feed a richer, more informed idea into the PRD generator.
When to use
• You've just finished a brainstorming session in Slack and need to formalize scattered ideas into a proper PRD before the next sprint planning meeting.
• A stakeholder pitched a new feature during a recorded meeting, and you want to quickly draft requirements while the context is fresh.
• You're preparing for a design review and need a structured document that covers UI specs, data models, and exception handling for engineering alignment.
• You need to validate whether an early-stage concept has enough substance by stress-testing it against acceptance criteria and non-functional requirements.
• You're onboarding a new engineer and need a clear, comprehensive requirements document for an existing initiative.
Prompt examples
Input: product_idea: "A browser extension that lets customer success managers highlight and annotate key passages in support tickets, then automatically syncs those annotations into our internal CRM as structured follow-up tasks with priority levels."
remio responds:
Here is your structured PRD:
1. Project Background and Objectives: Customer success teams lose critical context when switching between support platforms and the CRM. This extension reduces manual data entry by 60% and ensures no high-priority follow-up slips through the cracks.
2. User Stories: As a CS manager, I want to highlight a ticket passage and assign it a priority (P0-P3) so it auto-creates a CRM task (Priority: High). As a team lead, I want a dashboard view of all annotated tickets across my team (Priority: Medium).
3. Functional Specifications: The Annotation Module supports text highlighting with color-coded priority tags, inline note fields (max 500 chars), and error handling for unsupported ticket page formats. The Sync Module uses a REST API to push structured tasks to the CRM with retry logic on failure.
4. Non-functional Requirements: Sync latency under 3 seconds, compatibility with Chrome 110+ and Edge 110+, AES-256 encryption for annotation data in transit.
5. Acceptance Criteria: All P0-P3 annotations must appear in the CRM within 5 seconds. Extension must not increase page load time by more than 200ms.
Tip 1: Before running this prompt, search remio for any prior Slack threads or meeting transcripts where the product idea was discussed — paste key quotes directly into your product_idea input to give the PRD richer context and more accurate user stories.
Tip 2: Include your target user persona and one specific pain point in the input field. Vague ideas like "a dashboard tool" produce generic PRDs, while "a dashboard for ops managers drowning in manual reporting" yields precise, actionable specs.
Tip 3: Run the prompt iteratively — generate a first draft, then refine by adding constraints like tech stack, timeline, or compliance requirements to the product_idea field.
More tips
レミオは知識に関するあらゆるニーズを満たします
詳しい機能はこちら
ウェブサイト、ローカル フォルダー、ファイルからリソースをキャプチャします。
ナレッジベース全体から、信頼できる回答を即座に取得できます。
デスクトップ、ブラウザ、モバイルで使えるアシスタント。
無制限の無料録音と文字起こし、ボットなし。