PRD Writer (YouTube)
The PRD Writer (YouTube) prompt guides expert Senior Product Managers and YouTube Strategists in creating detailed Product Requirement Documents for YouTube-centric features, bridging creative content with technical development for engineers.
What is the PRD Writer (YouTube) prompt?
Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.
ROLE: You are an expert Senior Product Manager and YouTube Strategist specializing in bridge-building between creative content production and technical software development. Your expertise lies in translating high-level content goals into actionable Product Requirement Documents (PRDs) for internal tools, viewer-facing features, or platform integrations. GOAL: Your task is to draft a comprehensive Product Requirement Document for a new YouTube-centric feature or internal tool. You must ensure the document is clear enough for engineers to build from while remaining aligned with the creator’s unique workflow and audience needs. CONTEXT: Information to include in the PRD: - FEATURE NAME: [FEATURE NAME] - TARGET AUDIENCE: [TARGET AUDIENCE] - CORE PROBLEM: [CORE PROBLEM] - SUCCESS METRICS: [SUCCESS METRICS] - KEY CONSTRAINTS: [KEY CONSTRAINTS] INSTRUCTIONS: 1. Analyze the [CORE PROBLEM] and [TARGET AUDIENCE] to define a clear 'User Persona' and 'User Story' section. 2. Draft a 'Product Overview' that summarizes how this feature solves the specific pain points mentioned. 3. Detail the 'Functional Requirements' by breaking down exactly what the feature must do. Use a prioritized list (Must-have vs. Nice-to-have). 4. Outline the 'User Flow’ or ‘Technical Logic’—describe the step-by-step journey the user takes from discovery to completion within this feature. 5. Define 'Success Metrics' based on [SUCCESS METRICS], providing specific KPIs (e.g., Click-Through Rate, Average View Duration, or Internal Processing Time). 6. Address the [KEY CONSTRAINTS], suggesting technical workarounds or phased rollout plans to manage these limitations. 7. Include a 'Non-Functional Requirements' section covering performance, security, and scalability relevant to YouTube’s ecosystem. OUTPUT FORMAT: Generate the document using the following structure: - TITLE: [FEATURE NAME] Requirement Document - STATUS: Draft / Version 1.0 - EXECUTIVE SUMMARY: (2-3 sentences) - USER STORIES: (Format: As a [User], I want to [Action], so that [Benefit]) - FUNCTIONAL REQUIREMENTS: (Numbered list with priority tags) - USER INTERFACE & EXPERIENCE: (Descriptive text of the layout and interactions) - DATA & ANALYTICS: (Tracking requirements for [SUCCESS METRICS]) - RISKS & MITIGATIONS: (Based on [KEY CONSTRAINTS]) QUALITY BAR: The PRD must be professional, devoid of fluff, and highly technical yet accessible. It should anticipate edge cases and provide enough detail that a developer could begin a technical design doc without needing significant clarification. Use industry-standard PM terminology throughout.
What variables does the PRD Writer (YouTube) prompt use?
| Variable | What to put | Example |
|---|---|---|
| [FEATURE NAME] | The name of the new YouTube feature or tool being documented. | Live Stream Captioning Tool |
| [TARGET AUDIENCE] | The specific users or creators that the feature is intended for. | Live streamers generating high-volume content |
| [CORE PROBLEM] | The fundamental issue or pain point the feature aims to solve. | Lack of real-time accessibility for viewers of live streamed content |
| [SUCCESS METRICS] | The key performance indicators (KPIs) that will measure the feature's success. | Increased live stream watch time, caption accuracy rates |
| [KEY CONSTRAINTS] | Any technical, budgetary, or time limitations affecting feature development. | Low latency processing, integration with existing video pipeline |
How do I use the PRD Writer (YouTube) prompt?
- 1Identify a specific YouTube feature or internal tool you want to develop.
- 2Define the 'FEATURE NAME', 'TARGET AUDIENCE', 'CORE PROBLEM', 'SUCCESS METRICS', and 'KEY CONSTRAINTS'.
- 3Copy the prompt body and replace all bracketed variables with your specific information.
- 4Run the prompt and review the generated Product Requirement Document.
- 5Refine any sections as needed, collaborating with your team to finalize the PRD.
When should you use the PRD Writer (YouTube) prompt?
Developing New YouTube Creator Tools
Use this prompt to outline a PRD for an internal tool designed to streamline content creation or management for YouTube creators.
Designing Viewer-Facing Features
Employ this prompt when planning new audience engagement features or playback improvements on the YouTube platform.
Integrating Third-Party Services
Apply this prompt to draft documentation for integrating external services or APIs with YouTube's ecosystem, ensuring seamless functionality.
Refining Existing YouTube Functionality
Utilize this prompt to create PRDs for enhancements, redesigns, or optimization projects for existing YouTube features.
Training Junior Product Managers
An excellent resource for new product managers to understand the structure and depth required for a comprehensive PRD in a specific domain like YouTube.
What does the PRD Writer (YouTube) prompt output look like?
LIVE STREAM CAPTIONING TOOL Requirement Document STATUS: Draft / Version 1.0 EXECUTIVE SUMMARY: This document outlines the requirements for a new Live Stream Captioning Tool. It aims to enhance accessibility for live stream viewers by providing real-time, accurate captions, thereby increasing engagement and watch time. The tool will leverage advanced speech-to-text technology and integrate seamlessly into the existing YouTube live streaming infrastructure. USER STORIES: - As a viewer, I want to see accurate, real-time captions during a live stream, so that I can understand the content better if I'm hearing-impaired or in a noisy environment. - As a creator, I want an automatic captioning option for my live streams, so that I don't have to manually caption and can reach a wider audience. FUNCTIONAL REQUIREMENTS: 1. Real-time speech-to-text conversion (Must-have) 2. Display captions within the live stream player (Must-have) 3. Customizable caption display settings (e.g., size, color) (Nice-to-have) 4. Support for multiple languages (Nice-to-have) USER INTERFACE & EXPERIENCE: Viewers will activate captions via a new button on the live stream player interface. Captions will appear as an overlay, with options to adjust styling in the player settings. Creators will have a toggle in their live stream settings to enable or disable the feature. DATA & ANALYTICS: Track live stream watch time with captions enabled, user engagement with caption features (e.g., settings changes), caption accuracy rates (sampled), and viewer feedback on caption quality. RISKS & MITIGATIONS: Low latency processing for real-time captions is a technical challenge; mitigate by using parallel processing and optimizing speech recognition models. Initial caption accuracy may vary; plan for iterative model training and user feedback loops for continuous improvement.
Which AI model works best with the PRD Writer (YouTube) prompt?
Excellent for generating structured, detailed technical documentation and handling multiple input variables with high coherence.
Strong in understanding complex instructions and generating highly detailed, logically flowing documents, ideal for multi-section PRDs.
Proficient at producing clear, well-structured professional text, making it suitable for creating comprehensive and readable PRDs.
What are the pros and cons of the PRD Writer (YouTube) prompt?
Pros
- Generates detailed, structured PRDs for YouTube features.
- Bridges creative goals with technical requirements effectively.
- Includes essential sections like user stories, functional requirements, and success metrics.
- Promotes clear communication between product and engineering teams.
- Encourages consideration of constraints and non-functional requirements.
- Adaptable for internal tools or viewer-facing features.
Cons
- Requires user to provide specific, well-defined input for variables.
- May require manual refinement for highly nuanced technical specifications.
- Output length can be significant, potentially needing summarization for quick overviews.
How can you get better results from the PRD Writer (YouTube) prompt?
- Be as specific as possible with your variable inputs to ensure a tailored and accurate PRD.
- Consider running the prompt multiple times with different levels of detail in the variables to explore various outputs.
- After generating, review the 'Functional Requirements' and prioritize them further based on your specific project's roadmap and resources.
- Use the generated PRD as a robust starting point, then collaborate with engineering for deeper technical specifications.
- Provide examples within your variable inputs, especially for 'KEY CONSTRAINTS', to guide the AI's mitigation suggestions.
Frequently asked questions about the PRD Writer (YouTube) prompt
What is the PRD Writer (YouTube) prompt?
This prompt is designed to help Senior Product Managers and YouTube Strategists create comprehensive Product Requirement Documents (PRDs) for new YouTube-centric features, tools, or integrations. It translates high-level content goals into actionable technical specifications.
Who is this prompt for?
It is best suited for product managers, product owners, strategists, and anyone involved in defining and documenting the requirements for new software development within the YouTube ecosystem, whether for internal teams or external users.
What kind of output can I expect?
You can expect a professional, structured PRD including an executive summary, user stories, functional requirements, UI/UX considerations, data & analytics tracking, and risk mitigation strategies.
Do I need to be a technical expert to use this prompt?
While the prompt is designed for technical documentation, you primarily need to understand the product's vision and user needs. The AI assists in structuring and detailing the technical aspects based on your input.
Can I use this for non-YouTube related products?
While optimized for YouTube, the core structure of the PRD is broadly applicable. You can adapt the prompt by adjusting the 'CONTEXT' and 'ROLE' to suit other product domains, though results may vary.
How detailed should my input be for the variables?
The more specific and detailed your input for variables like 'CORE PROBLEM' and 'KEY CONSTRAINTS', the more tailored and effective the generated PRD will be. Concise but descriptive input works best.