Introduction
Research prompting is the practice of writing clear and controlled prompts that guide an AI model through a research task. It helps the model define a question, limit the scope, find useful evidence, compare sources, verify claims, detect contradictions, and produce a well-structured research report.
A general prompt such as “Research artificial intelligence” is too broad. It does not define what should be studied, which sources should be used, what time period matters, or how the final answer should be presented.
A strong research prompt turns the broad request into a controlled process.
For example:
Research the use of generative AI in software testing.
Focus on automated test generation and defect detection.
Use sources published from 2022 onward.
Prefer peer-reviewed papers, official documentation, and industry reports.
Separate confirmed facts from interpretations.
Cite every important factual claim.
Present the result as a structured research report.
This prompt gives the model a clear topic, scope, source rules, evidence requirements, and output format.
Why Research Prompting Is Important
Research tasks are more difficult than simple question-answer tasks because they require several connected activities:
- Understanding the research problem
- Defining boundaries
- Creating useful search terms
- Selecting trustworthy sources
- Collecting evidence
- Comparing different findings
- Checking whether claims are supported
- Identifying disagreements
- Combining information into a useful conclusion
- Providing citations
Without proper instructions, an AI model may:
- Produce a broad and unfocused answer
- Use weak or outdated sources
- Present assumptions as facts
- Miss conflicting evidence
- Create unsupported conclusions
- Add incorrect citations
- Mix source findings with its own interpretation
- Ignore important limitations
Research prompting reduces these problems by making the research process explicit.
Learning Objectives
After studying this chapter, you should be able to:
- Define a clear research question
- Set practical research boundaries
- Generate effective search queries
- Define source quality rules
- Compare multiple sources
- Collect evidence in a structured format
- Verify claims against supporting evidence
- Detect contradictions between sources
- Create literature review prompts
- Identify research gaps
- Synthesize findings from different sources
- Define citation requirements
- Separate facts from inferences
- Generate structured research reports
- Build reusable research prompt templates
Prerequisites
Before using research prompts, you should understand:
- Basic prompt structure
- Instructions and constraints
- Context and input data
- Output format control
- Source credibility
- Difference between facts and opinions
- Basic citation concepts
- Research ethics
- Limitations of AI-generated content
Access to browsing tools, search engines, databases, uploaded documents, or research papers may also be required for evidence-based research.
Key Terms
| Term | Meaning |
|---|---|
| Research question | The main question that the research must answer |
| Scope | The boundaries of the research |
| Search query | A phrase used to find relevant information |
| Primary source | Original evidence such as a research paper, dataset, law, or official record |
| Secondary source | A source that explains or analyses primary sources |
| Evidence | Information used to support a claim |
| Claim | A statement presented as true |
| Verification | The process of checking whether a claim is supported |
| Contradiction | A disagreement between two or more sources |
| Literature review | A structured analysis of existing research |
| Research gap | An area that has not been studied sufficiently |
| Synthesis | Combining findings from multiple sources |
| Citation | A reference showing where information came from |
| Inference | A conclusion drawn from available evidence |
| Limitation | A factor that reduces the strength or coverage of research |
Basic Research Prompt Structure
A reliable research prompt normally contains the following parts:
- Research role
- Research question
- Research scope
- Source selection rules
- Search instructions
- Evidence requirements
- Verification rules
- Citation requirements
- Output structure
- Limitations and uncertainty rules
Example:
Act as a technical research analyst.
Research how large language models are used in code review.
Focus on defect detection, security review, and maintainability.
Include studies and technical reports published from 2021 onward.
Prefer peer-reviewed research, official documentation, and established engineering organisations.
Exclude promotional articles without supporting evidence.
Compare findings from at least five independent sources.
Record evidence for every major claim.
Identify contradictions and explain possible reasons.
Separate verified facts from reasonable inferences.
Include citations with each major factual statement.
Present the result using an executive summary, methodology, findings, limitations, and conclusion.
Defining a Research Question
A research question defines exactly what the research must investigate. It is the foundation of the entire research process.
A weak question creates weak research because the model does not know what information is relevant.
Weak research question:
What is artificial intelligence?
This question is too broad. It may produce a general explanation instead of focused research.
Improved research question:
How does generative AI affect software developer productivity in enterprise application development?
A stronger version can include population, technology, comparison, outcome, and time period.
How has the use of generative AI coding assistants affected development speed, code quality, and defect rates among enterprise software teams since 2022?
Characteristics of a Strong Research Question
A useful research question should be:
- Clear
- Focused
- Researchable
- Specific
- Relevant
- Neutral
- Answerable using available evidence
Elements of a Research Question
A research question may define:
- Subject
- Population
- Technology
- Environment
- Comparison
- Outcome
- Time period
- Geographic area
Example:
Among Java development teams in large organisations, how does AI-assisted code generation affect delivery time and post-release defect rates compared with traditional development methods?
Prompt for Creating a Research Question
Act as a research design expert.
Convert the broad topic "AI in software development" into five focused research questions.
Each question must define the technology, target group, expected outcome, and time period.
Avoid questions that can be answered only with yes or no.
Make each question suitable for evidence-based research.
Explain why each question is researchable.
Expected Output
The model should produce focused questions such as:
- How do AI coding assistants affect task completion time among professional software developers?
- What types of coding defects are commonly introduced by AI-generated code?
- How does AI-assisted development affect code review effort in enterprise teams?
- What security risks are associated with accepting AI-generated code without manual verification?
- How do junior and senior developers differ in their use of AI coding tools?
Common Mistakes
- Asking a question that is too broad
- Combining many unrelated questions
- Using emotional or biased language
- Assuming the conclusion in advance
- Asking questions without measurable outcomes
- Ignoring the availability of evidence
Biased question:
Why are AI coding tools harmful to software developers?
Neutral version:
What benefits and risks do AI coding tools create for software developers?
Defining Research Scope
Research scope defines what will and will not be included in the study. It prevents the research from becoming too broad.
A scope may define:
- Topic boundaries
- Time period
- Geographic area
- Industry
- Population
- Technology
- Source types
- Language
- Required depth
- Excluded areas
Example scope:
Include research about generative AI coding assistants used by professional software developers.
Cover productivity, code quality, security, and developer learning.
Include sources published between January 2022 and December 2025.
Focus on enterprise software development.
Exclude studies focused only on student assignments.
Exclude articles without data, evidence, or named sources.
Why Scope Control Matters
Without scope control, the model may:
- Include unrelated information
- Mix old and new evidence
- Compare different industries incorrectly
- Use studies involving unsuitable participants
- Spend too much attention on background information
- Miss the main research objective
Prompt for Defining Scope
Act as a research planner.
Define a practical research scope for the question below.
Research question: How do AI coding assistants affect software developer productivity?
Define included topics.
Define excluded topics.
Define the target population.
Define the time period.
Define acceptable source types.
Define geographic limitations.
Define the expected research depth.
Present the scope as a research boundary table.
Scope Table Example
| Scope Area | Included | Excluded |
|---|---|---|
| Population | Professional developers | General consumers |
| Technology | AI coding assistants | General chatbots |
| Outcomes | Speed, quality, defects | Marketing performance |
| Period | 2022 onward | Older studies unless historically important |
| Sources | Papers, reports, official studies | Unsupported blogs |
| Environment | Enterprise software teams | School-level coding exercises |
Scope Validation Questions
Before starting research, ask:
- Is the topic too broad?
- Is the time period clear?
- Is the target population defined?
- Are source types specified?
- Are exclusions clearly stated?
- Can the question be answered within the available time and resources?
Generating Search Queries
Search queries are phrases used to find research sources. Good search queries improve the quality and relevance of collected information.
A single search query is rarely enough for a complete research task.
Broad query:
AI coding assistants
Focused queries:
AI coding assistants developer productivity empirical study
GitHub Copilot code quality research paper
generative AI software defects security study
AI pair programming enterprise development report
coding assistant productivity controlled experiment
Search Query Components
A search query may contain:
- Main topic
- Related term
- Research outcome
- Population
- Study type
- Date
- Source type
Example:
"AI coding assistant" AND "developer productivity" AND empirical study
Types of Search Queries
Broad discovery query
Used to understand the topic.
generative AI software development research
Focused evidence query
Used to find support for a specific claim.
AI coding assistant task completion time controlled experiment
Source-specific query
Used to search trusted websites or databases.
site:arxiv.org AI code generation security
site:acm.org AI coding assistant productivity
site:microsoft.com research Copilot developer productivity
Contradiction query
Used to find opposing evidence.
AI coding assistants reduce code quality study
limitations of AI coding assistants developer productivity
Recent research query
Used to locate newer evidence.
generative AI code review research 2025
Prompt for Search Query Generation
Act as an academic search strategist.
Generate 20 search queries for the research question below.
Research question: How do AI coding assistants affect software developer productivity and code quality?
Create broad discovery queries.
Create focused evidence queries.
Create opposing-view queries.
Create source-specific queries.
Create recent-research queries.
Include important synonyms and alternative technical terms.
Group the queries by purpose.
Do not repeat the same query with minor wording changes.
Query Expansion
The model should identify alternative terms.
| Main Term | Related Terms |
|---|---|
| AI coding assistant | Code assistant, AI pair programmer, code completion model |
| Productivity | Development speed, task completion time, throughput |
| Code quality | Maintainability, correctness, defect rate |
| Security | Vulnerability, insecure code, security defect |
| Developer | Programmer, software engineer, development team |
Search Query Validation
A useful query should:
- Contain the main concept
- Include at least one narrowing term
- Avoid unnecessary words
- Use recognised technical terminology
- Match the target source type
- Produce evidence relevant to the research question
Source Selection Criteria
Source selection criteria define which sources are acceptable. They help prevent weak, biased, outdated, or irrelevant material from influencing the research.
Common Source Quality Factors
Authority
Who created the source?
- University
- Government body
- Research organisation
- Professional association
- Established company
- Named subject expert
Evidence quality
Does the source provide:
- Data
- Methodology
- References
- Experiments
- Case studies
- Official records
- Reproducible findings
Relevance
Does the source directly address the research question?
Recency
Is the information recent enough for the topic?
Independence
Is the source independent, or is it promoting a product?
Transparency
Does the source explain how its conclusions were reached?
Peer review
Has the research been reviewed by qualified experts?
Source Hierarchy
A general source hierarchy may be:
- Peer-reviewed research papers
- Government publications
- Official standards
- University research
- Original datasets
- Technical reports from established organisations
- Reputable industry analysis
- Expert commentary with supporting references
- News reports
- General blogs
- Anonymous social media content
The hierarchy may change depending on the research topic.
For product behaviour, official technical documentation may be more useful than a general academic article.
For medical claims, peer-reviewed studies and public health authorities should receive higher priority.
Prompt for Source Selection
Act as a source evaluation specialist.
Evaluate each provided source for authority, relevance, evidence quality, recency, transparency, and possible bias.
Assign a score from 1 to 5 for each criterion.
Explain every score briefly.
Classify each source as high confidence, medium confidence, or low confidence.
Reject sources that do not provide enough evidence for factual claims.
Present the result in a comparison table.
Source Evaluation Table
| Source | Authority | Evidence | Relevance | Recency | Bias Risk | Decision |
|---|---|---|---|---|---|---|
| Peer-reviewed experiment | 5 | 5 | 5 | 4 | 1 | Include |
| Vendor marketing page | 3 | 2 | 4 | 5 | 5 | Use cautiously |
| Anonymous blog | 1 | 1 | 2 | 3 | 4 | Exclude |
Source Selection Rules Example
Prefer primary sources whenever available.
Use secondary sources for context and interpretation.
Do not rely on a single source for major conclusions.
Do not use anonymous articles for critical claims.
Mark vendor-funded studies clearly.
Prefer recent sources for fast-changing technology.
Keep older sources only when they are historically important.
Record the publication date and source organisation.
Source Comparison
Source comparison examines how different sources address the same question. It helps identify agreement, disagreement, methodological differences, and evidence strength.
A source should not be accepted only because it supports the expected conclusion.
Comparison Dimensions
Compare sources by:
- Research objective
- Methodology
- Sample size
- Target population
- Technology studied
- Data collection method
- Time period
- Main findings
- Limitations
- Funding source
- Confidence level
Source Comparison Prompt
Compare the provided research sources.
Identify the question addressed by each source.
Compare their methodologies.
Compare sample sizes and target populations.
Summarise the main findings.
Identify where the findings agree.
Identify where the findings disagree.
Explain whether the disagreements may result from different methods, samples, definitions, or time periods.
Rank the sources by evidence strength.
Do not decide based only on publication reputation.
Present the comparison in a structured table followed by a short analysis.
Comparison Table Example
| Factor | Source A | Source B | Source C |
|---|---|---|---|
| Method | Controlled experiment | Developer survey | Repository analysis |
| Sample | 100 developers | 2,000 developers | 500 projects |
| Outcome | Task speed | User perception | Defect patterns |
| Finding | Faster completion | Higher perceived speed | Mixed code quality |
| Main limitation | Small task set | Self-reported data | No direct productivity measure |
Correct Interpretation
These sources do not necessarily contradict each other because they measure different outcomes.
- Source A measures actual task speed.
- Source B measures developer perception.
- Source C measures code quality in repositories.
The prompt should require the model to compare equivalent claims rather than treating all findings as directly comparable.
Evidence Collection
Evidence collection is the process of recording information that supports or challenges a research claim.
Evidence should be collected in a structured form rather than stored as unorganised notes.
Evidence Record Fields
A useful evidence record may include:
- Evidence ID
- Claim
- Supporting text
- Source title
- Author or organisation
- Publication date
- Source type
- Page or section
- URL or identifier
- Evidence strength
- Limitations
- Researcher notes
Evidence Collection Prompt
Extract evidence from the provided sources for the research question below.
Research question: How do AI coding assistants affect developer productivity?
Record one evidence item per row.
Include the exact claim supported by the evidence.
Include the source title.
Include the publication date.
Include the page, section, or paragraph location when available.
Classify the evidence as supporting, opposing, or neutral.
Rate the evidence strength as strong, moderate, or weak.
Record important limitations.
Do not convert author opinions into factual evidence.
Do not add information that is not present in the source.
Evidence Table Example
| Evidence ID | Claim | Position | Source | Location | Strength | Limitation |
|---|---|---|---|---|---|---|
| E01 | AI assistance reduced task completion time | Supporting | Study A | Results section | Strong | Limited task types |
| E02 | Developers reported higher productivity | Supporting | Survey B | Table 4 | Moderate | Self-reported |
| E03 | Generated code contained security weaknesses | Opposing | Study C | Section 5 | Strong | Focused on selected languages |
Evidence Quality Levels
Strong evidence
- Directly supports the claim
- Uses clear methods
- Has enough data
- Can be independently checked
- Comes from a reliable source
Moderate evidence
- Supports the claim but has limitations
- Uses self-reported data
- Has a limited sample
- May not apply to all environments
Weak evidence
- Based mainly on opinion
- Lacks methodology
- Uses unclear data
- Comes from a highly biased source
- Cannot be independently checked
Claim Verification
Claim verification checks whether a statement is supported by sufficient and reliable evidence.
Example claim:
AI coding assistants always improve developer productivity.
This is an absolute claim. It requires strong evidence across many environments. A few studies showing improvement are not enough to support the word “always.”
A safer claim may be:
Several studies indicate that AI coding assistants can reduce completion time for selected programming tasks, although the effect varies by task type, developer experience, and evaluation method.
Claim Verification Process
- Extract the exact claim.
- Identify important terms.
- Determine the required evidence level.
- Find supporting evidence.
- Search for opposing evidence.
- Check source quality.
- Compare study conditions.
- Decide whether the claim is verified.
- Rewrite the claim when necessary.
- Record uncertainty.
Claim Status Labels
- Verified
- Partially verified
- Unsupported
- Contradicted
- Inconclusive
- Outdated
Claim Verification Prompt
Verify each claim using the provided evidence.
Match every claim with supporting or opposing evidence.
Check whether the source directly supports the full claim.
Identify words such as always, never, all, none, proven, and guaranteed.
Mark claims that are broader than the available evidence.
Classify each claim as verified, partially verified, unsupported, contradicted, or inconclusive.
Rewrite unsupported or overstated claims using accurate language.
Include the evidence IDs used for each decision.
Do not treat repeated claims from dependent sources as independent confirmation.
Verification Table Example
| Claim | Status | Evidence | Reason | Revised Claim |
|---|---|---|---|---|
| AI tools always improve productivity | Unsupported | E01, E02 | Evidence covers selected tasks only | AI tools may improve productivity for some tasks |
| AI-generated code can contain vulnerabilities | Verified | E03, E07 | Multiple direct studies support the claim | No revision required |
| Junior developers benefit more than experts | Inconclusive | E04 | Only one small study | Some evidence suggests different effects by experience level |
Triangulation
Triangulation means checking a claim using different evidence types.
For example:
- Controlled experiment
- Developer survey
- Repository analysis
- Industry case study
When different methods produce similar findings, confidence may increase.
Contradiction Detection
Contradiction detection identifies cases where sources make incompatible claims.
Example:
Source A:
AI coding assistants reduce task completion time.
Source B:
AI coding assistants do not improve overall delivery speed.
These statements may appear contradictory, but they may measure different outcomes.
- Task completion time may refer to a small coding exercise.
- Delivery speed may include testing, review, integration, and deployment.
The model must determine whether the contradiction is real or only apparent.
Types of Contradictions
Direct contradiction
Two sources make opposite claims about the same condition.
Scope contradiction
The findings apply to different populations or environments.
Definition contradiction
The sources define a term differently.
Method contradiction
Different research methods produce different results.
Time-based contradiction
A newer technology version behaves differently from an older version.
Measurement contradiction
The sources measure different outcomes.
Contradiction Detection Prompt
Analyse the provided sources for contradictions.
Extract claims that discuss the same research issue.
Identify claims that support each other.
Identify claims that appear to conflict.
Determine whether each conflict is direct or only apparent.
Compare definitions, samples, methods, time periods, technologies, and measured outcomes.
Explain the most likely reason for each disagreement.
Do not force a single conclusion when the evidence remains mixed.
Present unresolved contradictions clearly.
Contradiction Table
| Issue | Source A | Source B | Contradiction Type | Possible Explanation |
|---|---|---|---|---|
| Productivity | Faster coding tasks | No faster project delivery | Measurement | Task speed differs from delivery speed |
| Code quality | Fewer syntax errors | More security flaws | Outcome definition | Syntax quality differs from security quality |
| Developer benefit | Juniors improve more | Experts improve more | Sample or task type | Different experience groups and tasks |
Handling Unresolved Contradictions
When contradictions cannot be resolved, the report should state:
- What each source claims
- Why both sources may be credible
- Which differences may explain the conflict
- What additional research is required
- Why a final conclusion cannot yet be made
Literature Review Prompts
A literature review examines existing research on a topic. It does more than summarise papers separately. It identifies themes, methods, agreements, disagreements, trends, limitations, and research gaps.
Main Literature Review Activities
- Define the review question
- Define inclusion criteria
- Define exclusion criteria
- Search for studies
- Screen the results
- Extract important data
- Group studies by theme
- Compare methodologies
- Evaluate evidence quality
- Identify gaps
- Produce a structured synthesis
Basic Literature Review Prompt
Act as an academic research assistant.
Conduct a structured literature review on AI coding assistants and software developer productivity.
Include research published from 2022 onward.
Prefer peer-reviewed papers and original empirical studies.
Exclude articles that only provide opinions or product promotion.
Group the literature by productivity, code quality, security, developer experience, and learning effects.
Compare study designs, sample sizes, tools, programming languages, and evaluation measures.
Identify areas of agreement.
Identify conflicting findings.
Identify common limitations.
Identify unanswered research questions.
Cite every study discussed.
Present the result as a thematic literature review.
Literature Review Matrix
| Study | Research Question | Method | Sample | Main Finding | Limitation | Theme |
|---|---|---|---|---|---|---|
| Study A | Effect on speed | Experiment | 100 developers | Faster task completion | Small tasks | Productivity |
| Study B | Security impact | Code analysis | 500 outputs | Some insecure patterns | Limited languages | Security |
| Study C | Developer experience | Survey | 2,000 users | Higher satisfaction | Self-reporting | Experience |
Thematic Review Structure
A literature review may use this structure:
- Introduction
- Search methodology
- Study selection criteria
- Productivity findings
- Code quality findings
- Security findings
- Developer learning findings
- Contradictions
- Methodological limitations
- Research gaps
- Conclusion
Systematic Review Prompt
Create a systematic review protocol for the research question below.
Define databases to search.
Define search terms.
Define inclusion criteria.
Define exclusion criteria.
Define the screening process.
Define quality assessment criteria.
Define data extraction fields.
Define the synthesis method.
Define how disagreements between reviewers should be handled.
Do not claim that a systematic review was completed unless the full process was actually performed.
Research Gap Identification
A research gap is an important question or area that existing research has not answered sufficiently.
A gap is not simply a topic with few articles. It must be connected to a meaningful limitation in existing knowledge.
Common Types of Research Gaps
Population gap
A group has not been studied.
Example:
Most studies examine students rather than professional developers.
Method gap
Existing research relies on one method.
Example:
Most findings come from surveys rather than controlled experiments.
Technology gap
Research focuses on older tools or models.
Context gap
A specific industry or environment is missing.
Measurement gap
Important outcomes have not been measured.
Contradiction gap
Existing studies produce conflicting results.
Long-term gap
Most studies measure short-term effects only.
Geographic gap
Research is concentrated in a small number of countries.
Research Gap Prompt
Analyse the provided literature and identify research gaps.
Do not label a topic as a gap only because it is interesting.
Connect every proposed gap to evidence from the reviewed studies.
Identify missing populations.
Identify missing environments.
Identify missing outcome measures.
Identify methodological weaknesses.
Identify unresolved contradictions.
Identify areas lacking long-term data.
Explain why each gap matters.
Propose one research question for each gap.
Rank the gaps by importance and research feasibility.
Research Gap Table
| Gap | Evidence from Literature | Why It Matters | Proposed Question |
|---|---|---|---|
| Few long-term studies | Most studies lasted less than one month | Short-term gains may not continue | How does AI assistance affect productivity over one year? |
| Limited security evaluation | Many studies measure speed only | Faster code may still create risk | How does AI-generated code affect security defect rates? |
| Few enterprise studies | Many studies use students | Student results may not apply to companies | What is the effect in large enterprise teams? |
Weak Gap Statement
There is not enough research on AI.
This statement is too broad and unsupported.
Strong Gap Statement
Existing studies mainly measure short-term task completion speed in controlled settings. Limited evidence is available on whether the observed productivity gains continue across full enterprise development cycles that include design, review, testing, deployment, and maintenance.
Research Synthesis
Research synthesis combines information from multiple sources into a clear and evidence-based understanding.
Synthesis is different from summarisation.
A summary explains each source separately.
A synthesis connects sources and explains:
- What they collectively show
- Where they agree
- Where they disagree
- Which evidence is stronger
- What limitations remain
- What conclusion is justified
Weak Summary-Based Approach
Study A found faster task completion.
Study B found higher developer satisfaction.
Study C found security weaknesses.
This lists findings but does not connect them.
Strong Synthesis
Current evidence suggests that AI coding assistants can improve speed and perceived productivity for selected development tasks. However, these benefits do not automatically produce better software quality. Security-focused studies show that generated code may contain unsafe patterns, indicating that productivity gains depend on effective review, testing, and developer judgement.
Synthesis Methods
Thematic synthesis
Groups findings by topic.
Chronological synthesis
Explains how research changed over time.
Method-based synthesis
Groups studies by research method.
Evidence-strength synthesis
Gives more importance to stronger studies.
Argument-based synthesis
Builds a conclusion using supporting and opposing evidence.
Research Synthesis Prompt
Synthesize the provided evidence into a unified analysis.
Do not summarise each source separately unless necessary.
Group related findings into themes.
Explain where multiple sources support the same conclusion.
Explain where findings differ.
Give greater weight to stronger and more direct evidence.
Distinguish measured findings from author interpretations.
Include important limitations.
State only conclusions supported by the combined evidence.
Use cautious language when evidence is mixed.
Cite the supporting sources for every major conclusion.
Evidence Weighting
The synthesis should consider:
- Study design
- Sample size
- Directness
- Replication
- Source independence
- Relevance
- Recency
- Known limitations
A large number of weak sources should not automatically outweigh one strong and directly relevant study.
Citation Requirements
Citation requirements tell the model how sources should be referenced.
Without clear citation instructions, the model may:
- Omit citations
- Place citations only at the end
- Use incomplete source details
- Add references that do not support the claim
- Produce invented references
- Mix citation styles
- Cite secondary reporting instead of original research
Citation Rules
A strong research prompt may require:
- Citation for every major factual claim
- Original sources where possible
- Page or section numbers
- One consistent citation style
- A complete reference list
- Clear citation placement
- No invented references
- Labels for sources that could not be verified
Citation Prompt
Use citations for every major factual claim.
Place each citation immediately after the claim it supports.
Prefer the original research source instead of an article summarising it.
Include the author, title, publication, year, and persistent identifier when available.
Include page or section numbers for source-specific evidence.
Use APA 7 citation style.
Do not invent missing publication details.
Mark incomplete citation fields as unavailable.
Confirm that every reference is used in the report.
Confirm that every in-text citation appears in the reference list.
Citation Evidence Mapping
A citation should support the exact statement beside it.
Claim:
AI coding assistants reduced development time by 50%.
The cited source must provide evidence for:
- AI coding assistants
- Development time
- The 50% value
- The relevant environment
A source saying developers “felt more productive” does not support a measured 50% time reduction.
Citation Validation Prompt
Audit the citations in the report.
Check whether each citation exists.
Check whether each cited source supports the nearby claim.
Identify claims that require citations but do not have them.
Identify citations placed after claims they do not support.
Identify references that are listed but never cited.
Identify in-text citations missing from the reference list.
Do not correct missing details by guessing.
Present all citation problems in a validation table.
Common Citation Styles
| Style | Common Use |
|---|---|
| APA | Social science, education, business |
| IEEE | Engineering and computer science |
| MLA | Humanities |
| Chicago | History and publishing |
| Vancouver | Medical and scientific fields |
Separating Facts from Inferences
Research reports must clearly separate confirmed information from conclusions drawn from that information.
Fact
A fact is directly supported by a source or observed data.
Example:
The study included 120 software developers.
Inference
An inference is a conclusion drawn from one or more facts.
Example:
The results may be more applicable to professional developers than to beginners.
The second statement may be reasonable, but it is an interpretation.
Opinion
An opinion is a judgement or preference.
Example:
AI coding assistants are the best development tools ever created.
Prediction
A prediction describes a possible future outcome.
Example:
AI coding assistants may become standard in most enterprise development teams.
Fact and Inference Prompt
Analyse the research content below.
Label every important statement as fact, inference, opinion, prediction, or unsupported claim.
Link each fact to its supporting source.
Explain the evidence used for each inference.
Use phrases such as "the evidence suggests" for reasonable inferences.
Use phrases such as "it is possible" for uncertain interpretations.
Do not present predictions as established facts.
Rewrite unsupported statements using accurate uncertainty language.
Output Example
| Statement | Type | Support | Recommended Wording |
|---|---|---|---|
| The study included 120 developers | Fact | Study A, Methods | Keep as written |
| Experts benefit less than beginners | Inference | Limited comparison data | The evidence suggests that benefits may vary by experience |
| AI will replace programmers | Prediction | No direct proof | AI may change some programming responsibilities |
| AI code is always insecure | Unsupported | Evidence shows risk, not certainty | AI-generated code can contain security weaknesses |
Useful Language for Facts
- The study found
- The dataset shows
- The report states
- The experiment measured
- According to the official record
Useful Language for Inferences
- The evidence suggests
- This may indicate
- A reasonable interpretation is
- These findings imply
- One possible explanation is
Useful Language for Uncertainty
- The evidence is limited
- The result remains inconclusive
- More research is required
- The finding may not apply to all environments
- The available sources do not establish causation
Research Report Generation
Research report generation converts research findings into a structured document.
A strong report should explain:
- What was researched
- Why it was researched
- How sources were selected
- What evidence was found
- Where sources agree
- Where sources disagree
- What conclusions are justified
- What limitations remain
Standard Research Report Structure
- Title
- Executive summary
- Research question
- Objectives
- Scope
- Methodology
- Source selection criteria
- Findings
- Evidence analysis
- Contradictions
- Research gaps
- Limitations
- Conclusion
- Recommendations
- References
- Appendix
Research Report Prompt
Act as a professional research analyst.
Generate a research report using only the provided evidence.
Use the research question as the main focus.
Begin with an executive summary.
Explain the research scope and methodology.
Group findings by theme.
Compare supporting and opposing evidence.
Identify contradictions and unresolved questions.
Separate facts from inferences.
Include a confidence level for each major conclusion.
Discuss limitations.
Provide practical recommendations only when supported by evidence.
Cite every major factual claim.
Include a complete reference list.
Do not add unsupported facts.
Do not hide uncertainty.
Executive Summary Requirements
The executive summary should include:
- Main research question
- Most important findings
- Strongest evidence
- Major uncertainty
- Main conclusion
- Key recommendation
It should not introduce facts that are missing from the main report.
Confidence Labels
| Confidence | Meaning |
|---|---|
| High | Multiple strong and independent sources agree |
| Moderate | Evidence supports the conclusion but has limitations |
| Low | Evidence is limited, indirect, or conflicting |
| Inconclusive | Available evidence does not support a clear conclusion |
Research Report Validation Prompt
Review the research report for quality.
Check whether the report answers the research question.
Check whether the scope was followed.
Check whether every major claim has evidence.
Check whether citations support the claims.
Check whether facts and inferences are separated.
Check whether contradictions are presented fairly.
Check whether limitations are complete.
Check whether conclusions are stronger than the evidence.
Check whether recommendations follow from the findings.
List all required corrections before producing the revised report.
Research Prompt Templates
Research prompt templates provide reusable structures for common research tasks.
General Research Prompt Template
Act as a professional research analyst.
Research the following question: [RESEARCH QUESTION]
Research objective: [OBJECTIVE]
Include: [INCLUDED AREAS]
Exclude: [EXCLUDED AREAS]
Time period: [TIME PERIOD]
Geographic scope: [GEOGRAPHIC SCOPE]
Target population: [POPULATION]
Prefer these source types: [SOURCE TYPES]
Reject sources that: [REJECTION RULES]
Generate search queries before collecting evidence.
Compare findings from at least [NUMBER] independent sources.
Record evidence for every major claim.
Search for both supporting and opposing evidence.
Identify contradictions.
Separate facts from inferences.
State uncertainty clearly.
Use [CITATION STYLE] citations.
Present the result as [OUTPUT FORMAT].
Include methodology, findings, limitations, conclusion, and references.
Research Question Development Template
Act as a research design expert.
Broad topic: [TOPIC]
Target population: [POPULATION]
Main problem: [PROBLEM]
Expected outcome: [OUTCOME]
Time period: [TIME PERIOD]
Generate five focused research questions.
Make every question specific and researchable.
Avoid biased wording.
Avoid yes-or-no questions.
Explain the variables contained in each question.
Recommend the strongest question and explain why.
Research Scope Template
Define the research scope for this question: [RESEARCH QUESTION]
Specify included topics.
Specify excluded topics.
Specify the target population.
Specify the environment.
Specify the time period.
Specify the geographic area.
Specify acceptable source types.
Specify the minimum evidence quality.
Specify the expected depth.
Present the result as a scope table.
Identify possible scope risks.
Search Query Generation Template
Act as a research search strategist.
Research question: [RESEARCH QUESTION]
Generate broad discovery queries.
Generate focused evidence queries.
Generate primary-source queries.
Generate opposing-evidence queries.
Generate recent-research queries.
Generate source-specific queries.
Include synonyms and alternative technical terms.
Group queries by purpose.
Avoid duplicate queries.
Explain what each query is expected to find.
Source Evaluation Template
Evaluate the following source: [SOURCE]
Identify the author or organisation.
Identify the publication date.
Identify the source type.
Evaluate authority.
Evaluate relevance.
Evaluate evidence quality.
Evaluate methodology.
Evaluate transparency.
Evaluate possible bias.
Identify funding or commercial interests.
Assign an overall confidence level.
Decide whether to include, include cautiously, or exclude.
Explain the decision using evidence.
Evidence Extraction Template
Extract evidence from the provided content.
Research question: [RESEARCH QUESTION]
Extract only information relevant to the question.
Record one evidence item per row.
Include the supported claim.
Include the exact source location.
Include the source date.
Classify the evidence as supporting, opposing, or neutral.
Rate evidence strength.
Record limitations.
Do not add interpretations to the evidence field.
Mark missing information as unavailable.
Claim Verification Template
Verify the following claim: [CLAIM]
Define the exact meaning of the claim.
Identify the evidence required to verify it.
Find supporting evidence.
Find opposing evidence.
Evaluate source quality.
Check whether the evidence supports the full claim.
Identify exaggerated or absolute wording.
Classify the claim as verified, partially verified, unsupported, contradicted, or inconclusive.
Rewrite the claim using accurate language.
Provide citations for the decision.
Source Comparison Template
Compare the following sources: [SOURCE LIST]
Compare research objectives.
Compare methodologies.
Compare populations.
Compare sample sizes.
Compare definitions.
Compare time periods.
Compare measured outcomes.
Compare findings.
Compare limitations.
Identify agreements.
Identify contradictions.
Explain possible reasons for differences.
Rank sources by evidence strength.
Present the result in a comparison table.
Contradiction Detection Template
Identify contradictions across the provided sources.
Match claims discussing the same issue.
Identify direct contradictions.
Identify apparent contradictions.
Compare definitions, methods, populations, time periods, and outcomes.
Explain possible causes of disagreement.
Identify which source has stronger evidence.
Keep unresolved contradictions open.
Do not remove minority findings without explanation.
Present the result in a contradiction matrix.
Literature Review Template
Conduct a literature review on: [TOPIC]
Main research question: [RESEARCH QUESTION]
Include studies from: [TIME PERIOD]
Include these source types: [SOURCE TYPES]
Apply these inclusion criteria: [INCLUSION CRITERIA]
Apply these exclusion criteria: [EXCLUSION CRITERIA]
Group studies by theme.
Compare research methods.
Compare findings.
Identify agreements.
Identify contradictions.
Identify methodological limitations.
Identify research gaps.
Cite every study.
Present the result as a structured thematic literature review.
Research Gap Template
Analyse the existing research on: [TOPIC]
Identify population gaps.
Identify geographic gaps.
Identify methodological gaps.
Identify measurement gaps.
Identify technology gaps.
Identify context gaps.
Identify long-term evidence gaps.
Identify unresolved contradictions.
Connect every gap to evidence from the literature.
Explain why each gap matters.
Create a research question for each gap.
Rank gaps by importance and feasibility.
Research Synthesis Template
Synthesize the provided research evidence.
Main research question: [RESEARCH QUESTION]
Group findings by theme.
Combine findings that support the same conclusion.
Compare opposing findings.
Weight evidence by quality and relevance.
Separate measured results from author interpretations.
Identify limitations.
State confidence levels.
Avoid source-by-source summaries unless required.
Produce conclusions supported by the combined evidence.
Cite every major synthesis statement.
Citation Audit Template
Audit all citations in the provided research report.
Identify claims requiring citations.
Check whether every major factual claim has a citation.
Check whether each citation supports the nearby claim.
Check whether source details are complete.
Check whether citations use one consistent style.
Check whether every in-text citation appears in the reference list.
Check whether every listed reference is used.
Identify possible invented or unverifiable citations.
Do not fill missing details by guessing.
Present the issues and corrections in a table.
Fact and Inference Separation Template
Review the provided research content.
Label each important statement as fact, inference, opinion, prediction, or unsupported claim.
Connect each fact to evidence.
Explain the reasoning behind each inference.
Rewrite inferences using cautious language.
Rewrite predictions as possibilities.
Remove or correct unsupported claims.
Preserve the original meaning where evidence allows.
Present the result in a classification table.
Complete Research Report Template
Act as a senior research analyst.
Research question: [RESEARCH QUESTION]
Objective: [OBJECTIVE]
Scope: [SCOPE]
Time period: [TIME PERIOD]
Target audience: [AUDIENCE]
Preferred sources: [SOURCE TYPES]
Excluded sources: [EXCLUDED SOURCES]
Required citation style: [CITATION STYLE]
Use only verifiable evidence.
Compare multiple independent sources.
Search for supporting and opposing findings.
Separate facts from inferences.
Identify contradictions.
Identify research gaps.
Assign confidence levels to major conclusions.
Generate an executive summary.
Explain the methodology.
Present findings by theme.
Include evidence tables.
Include limitations.
Include practical recommendations supported by evidence.
Include a conclusion.
Include a complete reference list.
Do not invent facts, evidence, quotations, or citations.
End-to-End Research Prompting Workflow
A complete research workflow can be organised into the following stages.
Stage 1: Define the Problem
- Identify the broad topic
- Understand the purpose
- Identify the target audience
- Define the decision the research should support
Prompt:
Explain the research problem in one clear paragraph.
Identify the main decision this research should support.
Identify the target audience.
Identify the information required to make that decision.
Stage 2: Create the Research Question
- Convert the topic into a focused question
- Remove bias
- Define measurable outcomes
Prompt:
Convert the research problem into one primary research question and three supporting questions.
Make all questions neutral, focused, and researchable.
Stage 3: Define Scope
- Set boundaries
- Define inclusion and exclusion rules
- Define the time period
Prompt:
Define the research scope.
Include clear boundaries and exclusions.
Identify any scope decisions that may affect the conclusion.
Stage 4: Generate Search Queries
- Create broad and focused queries
- Add synonyms
- Search for opposing evidence
Prompt:
Generate search queries for discovery, verification, opposing evidence, and primary sources.
Stage 5: Select Sources
- Apply quality criteria
- Remove weak sources
- Record possible bias
Prompt:
Evaluate all candidate sources.
Include only sources that meet the defined quality requirements.
Stage 6: Collect Evidence
- Extract claims
- Record locations
- Rate evidence strength
Prompt:
Build an evidence table containing supporting, opposing, and neutral evidence.
Stage 7: Verify Claims
- Match claims to evidence
- Remove unsupported claims
- Correct exaggeration
Prompt:
Verify every major claim using the evidence table.
Rewrite claims that are stronger than the evidence.
Stage 8: Detect Contradictions
- Compare findings
- Explain differences
- Preserve unresolved issues
Prompt:
Identify contradictions and determine whether they result from different methods, samples, definitions, or time periods.
Stage 9: Synthesize Findings
- Group evidence by theme
- Weight stronger studies
- Create justified conclusions
Prompt:
Produce a thematic synthesis that combines the strongest available evidence.
Stage 10: Generate the Report
- Follow a clear structure
- Include citations
- State limitations
Prompt:
Generate the final report using only verified evidence.
Include confidence levels and unresolved questions.
Stage 11: Validate the Report
- Audit claims
- Audit citations
- Audit scope compliance
- Audit conclusions
Prompt:
Perform an independent quality review of the report.
Correct every unsupported claim, citation problem, contradiction, and scope violation.
Practical Example: Researching AI Coding Assistants
Research Objective
Evaluate whether AI coding assistants improve software development productivity without reducing code quality or security.
Research Question
How do AI coding assistants affect development speed, code quality, and security among professional software developers?
Scope
- Professional software developers
- Enterprise and production development
- Studies from 2022 onward
- Productivity, quality, security, and review effort
- Peer-reviewed papers and technical reports
- Exclude purely promotional claims
Search Queries
AI coding assistant developer productivity empirical study
generative AI code quality controlled experiment
AI generated code security vulnerability research
GitHub Copilot professional developers productivity
AI coding assistant code review effort
limitations of AI pair programming tools
enterprise AI coding assistant case study
Evidence Requirements
- At least two independent sources for major conclusions
- Original research preferred
- Supporting and opposing evidence
- Exact study conditions
- Clear limitations
- Citation for every numerical claim
Final Research Prompt
Act as a senior software engineering research analyst.
Investigate how AI coding assistants affect development speed, code quality, security, and code review effort among professional software developers.
Include evidence published from 2022 onward.
Prefer peer-reviewed studies, original experiments, repository analyses, and technical reports from established research organisations.
Exclude unsupported promotional claims.
Generate a search strategy before analysing findings.
Compare at least five independent sources.
Record the methodology, sample, measured outcomes, findings, and limitations of every major study.
Search for evidence supporting and challenging productivity benefits.
Identify whether reported productivity gains are measured or self-reported.
Distinguish task completion speed from complete project delivery speed.
Detect contradictions caused by different tools, tasks, languages, developer experience levels, or evaluation methods.
Separate facts from inferences.
Assign confidence levels to major conclusions.
Cite every factual and numerical claim.
Present the result using an executive summary, scope, methodology, evidence table, thematic findings, contradictions, limitations, research gaps, conclusion, and references.
Common Research Prompting Mistakes
Using an Overly Broad Topic
Weak:
Research cloud computing.
Improved:
Research how serverless computing affects cost and scalability for event-driven web applications.
Failing to Define Sources
Weak:
Find information about AI security.
Improved:
Use peer-reviewed security research, official vulnerability databases, standards, and technical reports from recognised security organisations.
Asking Only for Supporting Evidence
Weak:
Find evidence that AI improves productivity.
Improved:
Find evidence supporting and challenging the claim that AI improves productivity.
Treating All Sources Equally
A peer-reviewed study should not automatically receive the same weight as an anonymous blog.
Ignoring Time Periods
Fast-changing topics require recent sources.
Confusing Correlation with Causation
A study showing that AI users complete more tasks does not automatically prove that AI caused the difference.
Using Absolute Language
Avoid unsupported words such as:
- Always
- Never
- Completely
- Guaranteed
- Proven
- All
- None
Inventing Citations
The prompt must tell the model not to guess author names, titles, dates, or identifiers.
Mixing Facts and Interpretation
Every inference should be labelled and connected to supporting evidence.
Ignoring Contradictory Findings
Research reports must explain disagreements rather than hiding them.
Producing a Summary Instead of a Synthesis
A list of source summaries does not explain the combined meaning of the evidence.
Hiding Limitations
Every research result has boundaries. Limitations help readers understand where conclusions may not apply.
Best Practices for Research Prompting
- Begin with one clear research question.
- Define what is included and excluded.
- Specify the required source types.
- Prefer primary sources.
- Search for opposing evidence.
- Record evidence before writing conclusions.
- Compare equivalent outcomes.
- Check dates and technology versions.
- Separate measured findings from opinions.
- Use cautious language for uncertain conclusions.
- Require citations beside supported claims.
- Never allow missing source details to be guessed.
- Identify conflicts between sources.
- Explain why findings differ.
- Assign confidence levels.
- Include research limitations.
- Validate the final report independently.
- Update research when the topic changes quickly.
Research Prompt Quality Checklist
Before using a research prompt, confirm the following:
- Is the research question clear?
- Is the objective defined?
- Is the scope limited?
- Is the target population specified?
- Is the time period specified?
- Are acceptable source types defined?
- Are weak sources excluded?
- Are search query instructions included?
- Is supporting evidence required?
- Is opposing evidence required?
- Are claims linked to evidence?
- Are contradictions checked?
- Are facts separated from inferences?
- Are citation rules defined?
- Is the output format clear?
- Are uncertainty and limitations required?
- Is final verification included?
Final Complete Research Prompt
Act as a professional research analyst with expertise in evidence evaluation.
Research the following question: [RESEARCH QUESTION]
The purpose of the research is: [PURPOSE]
The target audience is: [AUDIENCE]
Include the following topics: [INCLUDED TOPICS]
Exclude the following topics: [EXCLUDED TOPICS]
Use the following time period: [TIME PERIOD]
Use the following geographic scope: [GEOGRAPHIC SCOPE]
Focus on the following population or environment: [POPULATION OR ENVIRONMENT]
Prefer primary sources, peer-reviewed studies, official records, standards, original datasets, and established technical reports.
Exclude anonymous, unsupported, highly promotional, or unverifiable sources.
Generate broad, focused, source-specific, recent, and opposing-evidence search queries.
Evaluate every source for authority, relevance, evidence quality, recency, transparency, and possible bias.
Record every major evidence item in a structured evidence table.
Include supporting, opposing, and neutral evidence.
Verify every major claim against its supporting evidence.
Identify claims that are exaggerated, incomplete, outdated, unsupported, contradicted, or inconclusive.
Compare source methodologies, populations, sample sizes, definitions, time periods, technologies, outcomes, and limitations.
Detect direct and apparent contradictions.
Explain possible reasons for conflicting findings.
Conduct a thematic synthesis instead of listing source summaries.
Give greater weight to stronger, direct, relevant, and independent evidence.
Identify population, method, technology, measurement, context, geographic, contradiction, and long-term research gaps.
Separate facts, inferences, opinions, and predictions.
Use cautious wording when evidence is limited.
Cite every important factual and numerical claim.
Place citations immediately after the supported claim.
Use [CITATION STYLE] consistently.
Do not invent authors, titles, quotations, publication details, identifiers, evidence, or citations.
Mark missing information as unavailable.
Present the final output using a title, executive summary, research question, objectives, scope, methodology, source criteria, evidence table, thematic findings, source comparison, contradictions, research gaps, limitations, conclusions, recommendations, confidence levels, and references.
Perform a final verification pass before presenting the report.
Confirm that every conclusion follows from the collected evidence.
Clearly state what remains unknown or inconclusive.
Conclusion
Research prompting transforms a broad information request into a controlled evidence-based process. A strong research prompt does not simply ask an AI model to collect information. It defines the research question, limits the scope, guides source selection, requires evidence, verifies claims, detects contradictions, separates facts from interpretations, and controls citation quality.
The most reliable research workflow follows this sequence:
- Define the research question.
- Define the scope.
- Generate search queries.
- Select trustworthy sources.
- Collect structured evidence.
- Verify claims.
- Detect contradictions.
- Review existing literature.
- Identify research gaps.
- Synthesize the evidence.
- Apply citation rules.
- Separate facts from inferences.
- Generate the research report.
- Validate the final output.
Research prompts cannot guarantee perfect accuracy. However, clear instructions, source controls, evidence mapping, contradiction checks, and final validation can significantly improve the reliability, transparency, and usefulness of AI-assisted research.
Frequently Asked Questions
What is research prompting?
It is the practice of writing clear, controlled prompts that guide an AI model through a research task - defining a question, limiting scope, finding evidence, comparing sources, verifying claims, detecting contradictions, and producing a structured, cited research report, instead of a broad open-ended request.
What makes a research question "strong" instead of "weak"?
A strong research question is clear, focused, researchable, specific, neutral, and answerable using available evidence - defining the subject, population, technology, comparison, outcome, and time period. A weak question like "What is artificial intelligence?" is too broad to produce focused research.
Why does research scope need explicit boundaries?
Without scope control, the model may include unrelated information, mix old and new evidence, compare different industries incorrectly, or lose focus on the main objective. Defining included/excluded topics, time period, population, and source types keeps the research from becoming unfocused.
What separates strong evidence from weak evidence in research prompting?
Strong evidence directly supports the claim, uses clear methodology, has enough data, and comes from a reliable, independently checkable source. Weak evidence is based mainly on opinion, lacks methodology, uses unclear data, or comes from a highly biased source.
How should a research prompt handle claims that use words like "always" or "guaranteed"?
It should flag absolute language as broader than what the evidence typically supports, and require the model to rewrite overstated claims with accurate, qualified wording - e.g. replacing "AI tools always improve productivity" with "AI tools may improve productivity for some tasks."
Are two sources that seem to disagree always a real contradiction?
No. A contradiction can be direct, or only apparent - the sources may define terms differently, use different methods, measure different outcomes, or study different populations or time periods. A good research prompt asks the model to distinguish real conflicts from apparent ones before concluding.
What's the difference between summarizing sources and synthesizing them?
A summary explains each source separately (Study A found X, Study B found Y). A synthesis connects the sources - explaining what they collectively show, where they agree or disagree, which evidence is stronger, and what conclusion is actually justified by the combined evidence.
What is a research gap, and how is it different from just an under-covered topic?
A research gap must connect to a meaningful limitation in existing knowledge - a missing population, method, technology, measurement, or long-term data - not simply a topic with few articles. A strong gap statement cites what existing studies actually show and explains why the missing piece matters.
Why should facts, inferences, opinions, and predictions be labeled separately in a research report?
A fact is directly supported by a source ("the study included 120 developers"). An inference is a conclusion drawn from facts. An opinion is a judgment. A prediction is a possible future outcome. Blurring these together lets speculation get presented with the same confidence as verified data.
What should a citation validation check look for?
Whether every major factual claim has a citation, whether each cited source actually supports the claim beside it (not just a related topic), whether every in-text citation appears in the reference list and vice versa, and whether any citation details look invented rather than verified.