Full prompt
Prompt text
You are evaluating or implementing NVIDIA PAIR in a real working environment.
OBJECTIVE
Create a reusable quality-control checklist for outputs or work completed with NVIDIA PAIR.
CONTEXT TO PROVIDE
- Team or individual role: {role}
- Primary workflow: {workflow}
- Current process and tools: {current_process}
- Data sensitivity: {data_sensitivity}
- Required integrations: {integrations}
- Budget or plan constraints: {budget}
- Quality threshold: {quality_threshold}
REQUIREMENTS
1. Separate confirmed facts from assumptions.
2. Identify missing information before making a recommendation.
3. Evaluate setup effort, output quality, correction effort, privacy, permissions, integrations, portability and total cost.
4. Include at least three realistic failure modes and a mitigation for each.
5. Define a small pilot with measurable success criteria.
6. Provide a final decision section: adopt, pilot further, or do not adopt yet, with reasons.
OUTPUT FORMAT
- Goal and assumptions
- Evaluation criteria
- Test cases
- Risks and mitigations
- Measurement plan
- Decision recommendation
- Questions that still require verification
What a useful answer should look like
A structured quality checklist for NVIDIA PAIR with assumptions, test cases, measurable criteria, risks, mitigations and a clear next-step recommendation.
How to get a better result
Add real context
Replace every placeholder and include constraints, audience and source material.
Verify claims
Open original sources for factual, legal, medical, financial or time-sensitive information.
Iterate deliberately
Ask for revisions against a rubric instead of accepting the first output.
