Skip to content
Content
Skill

/amann-literature-synthesis

Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration. Builds the corpus

From plugin
awesome-journal-skills
1.4k200 skills

Claude Code

$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-literature-synthesis --agent claude-code

SKILL.md

amann-literature-synthesis.SKILL.md
name: amann-literature-synthesis
description: Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration. Builds the corpus and synthesis notes; it does not impose the organizing spine (amann-organizing-framework) or write prose.

Literature Synthesis Methodology (amann-literature-synthesis)

When to trigger

  • The proposal was invited and it is time to read the field thoroughly and transparently
  • Reading feels unsystematic; you fear missing streams a referee could name
  • You have many papers but no way to code, compare, or reconcile them
  • You must decide whether this review is narrative, systematic, or bibliometric in method

At Annals you synthesize — you do not run primary research

The folder name says "data analysis," but an Annals review reports **no data of its own**. Your "analysis" is the **systematic appraisal and integration of a literature**. The credibility of the whole review rests on the reader's belief that you read **everything that matters** and coded it consistently. Build coverage as a transparent process, not from memory.

Choose the integration method first

| Method | What it does | Best when | |--------|--------------|-----------| | **Narrative / integrative review** | reads, interprets, and reorganizes the literature into a new framework | the contribution is conceptual integration (Annals' core mode) | | **Systematic review** | a pre-specified, reproducible search-and-screen protocol; transparent inclusion | the field is large and you must prove comprehensive, unbiased coverage | | **Bibliometric / meta-analytic** | co-citation, co-word, or quantitative effect-size synthesis | the contribution is structural (intellectual map) or a cumulative magnitude estimate |

Most Annals reviews are **integrative narrative** with a **systematic backbone**: a transparent search establishes coverage, and the narrative does the reorganizing. Bibliometrics can *support* the framework but rarely replaces the interpretive contribution.

Building coverage to saturation

1. **Seed set.** Start from the proposal's key references and the field's canonical pieces. 2. **Transparent search.** Search the major databases (Web of Science, Scopus, EBSCO/Business Source, Google Scholar) by topic keywords; record terms, databases, dates, and counts so the "Review scope and process" claims are auditable. 3. **Forward + backward snowball.** Backward: each paper's reference list. Forward: who cites the seeds. Iterate until new searches stop turning up unseen important work (*saturation*). 4. **Inclusion / exclusion logic, stated.** Define what is in and out (time window, journal tier, theoretical vs. empirical, allied fields) and apply it consistently — referees ask "why did you omit X?" 5. **Working papers + adjacent literatures.** A current review must reach recent work and the bordering fields (organizational psychology, sociology) the literature draws on, or it reads stale or siloed. 6. **Saturation log.** Record when each search stopped yielding new must-cite work — this is your evidence of comprehensiveness for `amann-evidence-standards` and the referees.

From reading to synthesis (a coding matrix, not a summary)

Summarizing restates each paper; **synthesizing** makes papers *talk to each other*. Code the corpus as you read:

| Column | What to capture | |--------|-----------------| | Study | author–year; the contribution you cite it for | | Construct / question | exactly what it theorizes or measures (so incommensurable work is not pooled) | | Theory base | the lens it uses (so you can map streams and detect silos) | | Method / context | design, sample, setting (so you can weight credibility) | | Finding / claim | direction + magnitude or the conceptual move | | Tension | which work it agrees/conflicts with, and *why* |

This matrix feeds the organizing framework, the synthesis tables, and the even-handed treatment of debates. You **appraise** the studies (you are the field's reviewer-of-record); you do **not** re-run or "correct" them.

Checklist

  • [ ] Integration method chosen and justified (narrative-integrative / systematic / bibliometric)
  • [ ] Seed set drawn from canonical pieces + proposal references
  • [ ] Search terms, databases, dates, and counts recorded for the "scope and process" account
  • [ ] Forward and backward snowball iterated to saturation
  • [ ] Inclusion/exclusion logic stated and applied consistently
  • [ ] Recent working papers and adjacent literatures included (no staleness, no silo)
  • [ ] Saturation log records where searches stopped yielding new must-cites
  • [ ] Coding matrix captures construct + theory base + method + finding + tensions
  • [ ] Incommensurable constructs flagged (not pooled into a false "the literature finds…")
  • [ ] No major author/stream whose omission a referee could name

Anti-patterns

  • Reviewing from a personal reading list (predictable coverage gaps a referee will spot)
  • Summarizing paper-by-paper instead of synthesizing across the corpus
  • Pooling studies that theorize *different* constructs into one "the field shows…" claim
  • An undocumented search with no terms, databases, or counts — coverage claims become unfalsifiable
  • Ignoring working papers (stale) or adjacent literatures (siloed)
  • Re-estimating or "fixing" primary studies — an Annals review appraises, it does not re-run

Output format

【Method】narrative-integrative / systematic / bibliometric — and why
【Seed set】<canonical + proposal references>
【Search record】terms / databases / dates / counts logged? Y/N
【Snowball】backward+forward iterated to saturation? Y/N
【Inclusion logic】stated and consistently applied? Y/N
【Frontier + adjacency】recent WPs + bordering fields included? Y/N
【Saturation evidence】<where searches stopped yielding new must
Read more
@brycewang-stanford
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

1.4k200 skills
Get the whole plugin

Stars on GitHub

Momentum

stars in total
1.4k
Star history of brycewang-stanford/Awesome-Journal-Skills on GitHub, a chart by star-history.com

Other skills on awesome-journal-skills.

More skills from other plugins.

prompt-lookup

prompt-lookup

Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…

@gh-f@gh-fInstall Skill
ppt-master

ppt-master

AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…

@hugohe3@hugohe3Install Skill
morph-ppt

morph-ppt

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…

officecli13d33k
@iofficeai@iofficeaiInstall Skill

Questions about amann-literature-synthesis.

Which coding agents can use amann-literature-synthesis?
amann-literature-synthesis installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.