From pm-research
Structure and write a literature review for any research topic. Use when asked to write a literature review, systematic review summary, narrative review, or research background section. Produces a structured review with thematic organisation, critical analysis, and gap identification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-research:literature-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structures and writes literature reviews — from background sections of a dissertation through to standalone narrative reviews for publication.
Structures and writes literature reviews — from background sections of a dissertation through to standalone narrative reviews for publication.
Databases: [PubMed, EMBASE, PsycINFO, etc.] Search terms: [Key terms and Boolean combinations] Inclusion criteria: Study types, population, date range, language Exclusion criteria: [List] Results: [n] identified → [n] after deduplication → [n] screened → [n] included
Organised thematically — not chronologically. Each theme = one section.
Structure per thematic section:
[Theme heading]
[Opening: state what this section covers and what evidence shows overall]
[Evidence synthesis: present what multiple studies found, compare and contrast. Do NOT summarise one paper then the next — synthesise across them: "Three studies found X (Smith, 2019; Jones, 2020; Lee, 2021), while two found Y, with the difference attributable to..."]
[Critical analysis: note methodological strengths and weaknesses — sample sizes, study designs, generalisability, risk of bias]
[Closing: transition to next theme]
| Author, year | Study design | Population | n | Key findings | Quality/Limitations |
|---|
Well-established: [What literature consistently shows] Contested: [Areas where evidence is mixed and why] Missing: [Gaps the field needs to address] How your study addresses the gap: [If this is for a research proposal]
[3-5 sentences. Current state of knowledge and what is needed next]
For each paper: internal validity, external validity, bias types, effect size significance vs clinical significance, funding conflicts.
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-researchGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026