When should you use it?
- You need a first-pass systematic review for a thesis, grant or policy brief
- Your topic fits a PICO-style question
- You can spend time checking the screening log
Not for: Reviews you will publish without redoing the screening; Topics where most key papers sit behind paywalls you cannot access
What do you need, and what do you get?
You need
- Topic and the population, intervention, comparison and outcome you care about
- Inclusion and exclusion rules
- Which databases to search and which years
You get
- Edited research questions
- Screening criteria
- Included-paper table with a reason for each
- Extracted data
- Review draft plus a PRISMA-style chart of screening counts
How does it work, step by step?
- Ask for the protocolStart with a one-line request on your topic and let the agent propose PICO questions.
- Edit the questionsTighten the population, outcome and comparison so the scope matches what you actually need.
- Fix the screening rulesRewrite the draft include and exclude criteria; this is where most bad reviews go wrong.
- Pick sourcesChoose the databases and the date window before any search runs.
- Audit the outputCheck a sample of included and excluded papers against your rules, and read the full text of anything central.
The prompt
Our own prompt, inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD) and written to work in Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Topic: {topic}. Population: {population}. Intervention or exposure: {intervention}. Comparison: {comparison}. Outcomes: {outcomes}. Step 1 only: propose 2 to 3 PICO research questions and draft inclusion and exclusion criteria. Stop and wait for my edits. After I approve, search {databases} for {date_range}, deduplicate, screen titles and abstracts, then full text. Log every exclusion with a reason, mark papers you could not get in full, extract {data_fields}, and give an included-paper table plus a PRISMA-style count of each stage.
Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD): Systematic literature reviews take 12-18 months to complete. Looks like AI is going to fully automate systematic.... The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Paywalled full texts can drop out silently; check which included papers were screened on abstract only.
- A PRISMA diagram looks rigorous even when the criteria were loose; the numbers are only as good as your rules.
- Extracted figures can be misread; verify each one you cite against the paper.
Our take
This is the right shape for an automated review: the agent proposes, you edit at the two points that decide everything, and only then does the long mechanical part run. The questions and the screening rules are where bias enters, so keep those human. Never let the agent write the conclusions without your rewrite. Choose the databases and date window yourself before any search runs, and check a sample of included and excluded papers against your rules afterwards. Paywalled full texts can drop out silently, so note which papers were screened on abstract only. A neat PRISMA diagram can hide loose criteria; its numbers are only as good as your rules. Verify every extracted figure against the paper before citing it. For a published review, redo the screening properly. Rewriting the include and exclude criteria yourself is the step that matters most, and you should write the conclusions in your own words rather than adopting the agent's draft.
Where the time goes back: The protocol drafting, deduplication and first screening pass, the slowest parts of a review, arrive in one run you can check instead of build.
FAQ
Is this a publishable review?
What limits it?
Source and credit
Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Systematic literature reviews take 12-18 months to complete. Looks like AI is going to fully automate systematic...
- Creator
- Mushtaq Bilal, PhD (@MushtaqBilalPhD)
- Published on
- X
- Original date
- Apr 12, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.