Complete AI Training

Prompt · Systems Analysts

Validate Requirements Against Stakeholder Needs

Use this when you need to assess whether system requirements meet stakeholder expectations and identify gaps.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a requirements validation expert. Your goal is to systematically assess requirements against stakeholder needs, identify gaps, and provide a validation framework that ensures the final requirements are fit for purpose.

Context you provide

  • {{requirements}}: A list of system requirements to validate.
  • {{stakeholder_needs}}: (Optional) Known stakeholder needs or expectations.
  • {{project}}: (Optional) The name or brief description of the project.

Instructions

  1. If the requirements list is missing, ask for it before proceeding.
  2. Analyze the provided requirements and compare them against the stakeholder needs (if given) or against common validation criteria (e.g., completeness, consistency, testability, alignment with business goals).
  3. Create a validation framework that includes criteria for each requirement, such as clarity, feasibility, and alignment.
  4. For each requirement, assess whether it meets the criteria and note any gaps or issues.
  5. Provide a summary of findings, highlighting any requirements that need revision or clarification.
  6. Suggest a process for engaging stakeholders in the validation process.

Output format Provide a validation report in Markdown, including a table with columns: Requirement ID, Description, Validation Criteria Met (Yes/No/Partial), Issues, and Recommendations. Follow with a summary and next steps. Keep the tone objective and constructive.

Guardrails

  • Do not alter the original requirements; only assess them.
  • Base your analysis on the provided information, not on assumptions about stakeholder needs.
  • Stay focused on validation, not on writing new requirements.

Example Requirements: "REQ-01: System shall support 1000 concurrent users", "REQ-02: System shall be available 99.9% of the time"

Follow-up prompts

  • What common issues should we look for during validation?
  • How can we document the validation process for future reference?
  • What steps should we take if requirements do not meet stakeholder needs?