Back to Prompt Library
To establish a clear understanding of the problem space and define comprehensive requirements for the AI solution.

Problem Definition and Requirements Gathering

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Medical Diagnostics: Design an AI system to assist in preliminary diagnosis from symptom descriptions

Format
Text-first
Lines
21
Sections
9
Linked challenge
Medical Diagnostics: Design an AI system to assist in preliminary diagnosis from symptom descriptions

Prompt source

Original prompt text with formatting preserved for inspection.

21 lines
9 sections
No variables
16 checklist items
Welcome to the "Medical Diagnostics: Design an AI system to assist in preliminary diagnosis from symptom descriptions" challenge!

Your task is to design and build an AI-powered solution that addresses the following problem:

Build a healthcare-focused AI system that medical diagnostics: design an ai system to assist in preliminary diagnosis from symptom descriptions. Ensure compliance with medical standards while leveraging AI to improve patient outcomes and healthcare efficiency.

Let's start by clearly defining the problem space and gathering requirements:

1. **Problem Analysis**: Break down the core problem this challenge aims to solve. What are the pain points? Who are the primary users? What are the current limitations in existing solutions?

2. **User Requirements**: Define the key user requirements for your solution:
   - Primary use cases and user scenarios
   - Essential features and functionalities
   - Performance expectations
   - User interface/experience requirements

3. **Technical Requirements**: Identify the technical aspects:
   - AI/ML capabilities needed
   - Data requirements and sources
   - Integration points with existing systems
   - Scalability and performance targets

4. **Success Criteria**: Define what success looks like:
   - Key performance indicators (KPIs)
   - User satisfaction metrics
   - Business impact measurements
   - Technical benchmarks

Please provide a comprehensive analysis addressing each of these points. This will form the foundation for your solution design.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Preserve the source structure until you know which part of the prompt is actually driving the result quality.

Tune next

Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.

Verify after

Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.