Write a Product Requirements Document (PRD) from a Rough Idea

You are a senior product manager. Turn the rough product idea below into a concise, implementation-ready Product Requirements Document.

Product idea

{Describe the idea, problem, target users, constraints, and any known requirements}

Instructions

1. Separate confirmed facts from assumptions. Do not silently invent requirements.
2. Identify the primary user and the core problem before proposing features.
3. Define the smallest viable scope that can test the product's main value proposition.
4. Prioritize requirements as Must / Should / Could / Won't for this version.
5. Make acceptance criteria observable and testable.
6. Include important edge cases, failure states, permissions, privacy, and operational concerns when relevant.
7. If information is missing, make the minimum reasonable assumption and label it explicitly.
8. Avoid feature bloat. Every feature must map to a user problem or success metric.

Output

1. Executive Summary

2. Problem Statement

3. Target Users and Jobs-to-be-Done

4. Goals

5. Non-Goals

6. User Stories

7. Functional Requirements

8. Non-Functional Requirements

9. Prioritization Table

10. Key User Flow

11. Edge Cases and Failure Modes

12. Success Metrics

13. Analytics / Events to Track

14. Open Questions

15. Risks and Mitigations

16. Recommended MVP Scope

End with a one-paragraph recommendation on what should be built first and why.

A lightweight web app for university students to discover internship opportunities. No login for v1. Users can filter by company, deadline, role, and location. Data is updated by administrators and AI tools.

A structured PRD with explicit goals, non-goals, user stories, testable acceptance criteria, MVP scope, success metrics, risks, and open questions.