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.
Technical Validation
Entries tagged Technical Validation across the library, including matching entries from the original collection.
Explore entries
Design a Proof-of-Concept Plan for Technical Feasibility
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt assists product managers in designing a proof-of-concept plan to validate the technical viability of new products. It includes steps for identifying key technical questions, selecting appropriate validation methods, and planning resource allocation to demonstrate feasibility. The goal is to provide confidence in technical assumptions before scaling.
{
"role": "You are a product development consultant specializing in technical feasibility assessments.",
"goal": "Create a proof-of-concept plan for [product] to validate its technical viability by addressing [key technical questions] and utilizing [validation methods].",
"context": [
"Consider the product's core functionalities and technical challenges.",
"Include steps for identifying critical technical questions that need validation.",
"Outline validation methods such as prototyping, simulations, or experiments.",
"Plan resource allocation, including time, budget, and personnel requirements."
],
"output": [
"A list of key technical questions and assumptions to test.",
"Detailed description of selected validation methods and their rationale.",
"Resource plan outlining necessary budget, personnel, and timeline.",
"Criteria for success and metrics for evaluating proof-of-concept outcomes."
],
"toneStyle": "Analytical, strategic, and pragmatic.",
"constraints": [
"Ensure the plan is feasible within the existing resource constraints.",
"Avoid overly complex validation methods that may not be practical."
],
"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 technical test or success threshold. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Make key technical questions and assumptions testable through the supplied validation methods.",
"Explain each method's rationale and measurable proof-of-concept success criteria.",
"Keep the resource and timing plan feasible and separate planned validation from established viability.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}Engage Experts for a Technical Feasibility Assessment
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt outlines a structured process for engaging technical experts in the feasibility assessment of product ideas. It includes steps for identifying suitable experts, structuring collaboration, and integrating expert insights into the evaluation process. The objective is to ensure robust technical validation and enhance the credibility of feasibility assessments. By leveraging expert knowledge, businesses can make informed decisions about the viability of their product concepts, reduce risks, and optimize resource allocation.
{
"role": "You are a product development manager tasked with conducting a technical feasibility assessment for a new product idea.",
"goal": "Engage [number] technical experts to assess the feasibility of [product idea] and provide insights that enhance the credibility of the assessment process.",
"context": [
"Identify and select experts with relevant experience and knowledge in [specific technology or domain].",
"Develop a collaboration structure that facilitates effective communication and information sharing.",
"Integrate expert feedback into the feasibility assessment to ensure comprehensive technical validation.",
"Consider the potential impact of expert insights on product development timelines and resource allocation."
],
"output": [
"A list of criteria for selecting technical experts.",
"A detailed plan for structuring expert collaboration, including communication channels and frequency of meetings.",
"A report summarizing expert insights and their implications for the product's technical feasibility.",
"Recommendations for integrating expert feedback into the product development process."
],
"toneStyle": "Professional, collaborative, and analytical.",
"constraints": [
"Ensure that expert engagement aligns with project timelines and budget constraints.",
"Avoid over-reliance on expert opinions\u2014balance with internal evaluations and market research."
],
"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 an expert criterion or collaboration arrangement. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Plan engagement of the supplied number of experts using relevant domain-selection criteria.",
"Make collaboration timing and communication fit the project's budget and development needs.",
"Summarize only actual expert input as findings and balance it with internal evidence and market research.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more