Search the whole librarySearch and tags
Advanced AI Library. Three Ways to Use It.
Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.
Each resource is structured for all three.
Category counts cover all available entries.
Choosing a category or subcategory updates the results. Search and tag filters stay selected.
Comprehensive
Entries tagged Comprehensive across the library, including matching entries from the original collection.
Explore entries
Develop a Comprehensive Template for Product Requirements Documentation
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt is designed to assist product managers and development teams in creating a structured template for capturing and organizing product requirements. The objective is to ensure that all necessary details are covered in a comprehensive yet concise manner, facilitating effective communication and understanding among stakeholders. The template should streamline the documentation process, making it efficient and easy to update as requirements evolve.
{
"role": "You are a product development consultant specializing in creating efficient documentation templates.",
"goal": "Develop a comprehensive template for [product] requirements documentation that captures all necessary details efficiently and concisely.",
"context": [
"Consider the typical structure and elements needed for effective product requirements documentation.",
"Include sections for functional and non-functional requirements, user stories, and acceptance criteria.",
"Provide guidelines for maintaining clarity and brevity in the documentation.",
"Factor in the need for adaptability to accommodate changes in product scope and objectives."
],
"output": [
"A structured template with headings and subheadings for each major section.",
"Guidelines for writing clear and concise requirement descriptions.",
"Examples of well-written user stories and acceptance criteria.",
"Tips for keeping the documentation updated and relevant."
],
"toneStyle": "Professional, clear, and user-friendly.",
"constraints": [
"Ensure the template is adaptable to different product types and development methodologies.",
"Avoid overly complex or technical language that may hinder understanding."
],
"startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
"followUpQuestions": "After presenting the result, only if meaningful uncertainty remains or a useful refinement would improve it, ask up to [3] concise follow-up questions to refine a documentation section or example. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Include organized sections for functional and non-functional requirements, user stories, and acceptance criteria.",
"Make guidance and examples concise, clear, and internally consistent.",
"Explain how documentation stays current as scope changes without prescribing an unnecessarily complex methodology.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more