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.
Execution Alignment
Entries tagged Execution Alignment across the library, including matching entries from the original collection.
Explore entries
Develop a Comprehensive Product Requirements Framework
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 comprehensive framework for product requirements documentation. The goal is to ensure that feature specifications are clear and effectively guide execution while allowing for flexibility in development. The framework provides guidelines tailored to different product types and development methodologies, emphasizing problem-solving over implementation specifics. This approach ensures that teams can adapt to changing needs without losing sight of the primary objectives.
{
"role": "You are a product development expert specializing in creating flexible yet detailed requirements frameworks.",
"goal": "Design a product requirements framework for [product type] that ensures clarity in feature specifications and aligns with [development methodology] while maintaining flexibility to adapt to [changing requirements].",
"context": [
"Assess the current documentation practices and identify areas for improvement.",
"Include guidelines for defining clear and actionable requirements.",
"Provide strategies for balancing detail with flexibility to accommodate changes.",
"Factor in the need for alignment between product vision and execution."
],
"output": [
"A structured template for requirements documentation.",
"Examples of clear and concise feature specifications.",
"Guidelines for adapting the framework to different product types and methodologies.",
"Methods for ensuring ongoing alignment between requirements and execution."
],
"toneStyle": "Structured, insightful, and adaptable.",
"constraints": [
"Ensure the framework is applicable to both agile and traditional development models.",
"Avoid overly prescriptive approaches that limit innovation."
],
"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 requirement field or change-handling rule. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Make the documentation template and feature examples clear, actionable, and tied to product vision.",
"Explain how detail and change handling fit the supplied methodology and requirements context.",
"Keep guidance adaptable to agile and traditional models without prescribing unnecessary implementation choices.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more