本文へ移動
cccskills
無料GitHub で公開

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 and synthesis notes; it does not impose the organizing spine (amann-organizing-framework) or write prose.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

MethodWhat it doesBest when
Narrative / integrative reviewreads, interprets, and reorganizes the literature into a new frameworkthe contribution is conceptual integration (Annals' core mode)
Systematic reviewa pre-specified, reproducible search-and-screen protocol; transparent inclusionthe field is large and you must prove comprehensive, unbiased coverage
Bibliometric / meta-analyticco-citation, co-word, or quantitative effect-size synthesisthe 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:

ColumnWhat to capture
Studyauthor–year; the contribution you cite it for
Construct / questionexactly what it theorizes or measures (so incommensurable work is not pooled)
Theory basethe lens it uses (so you can map streams and detect silos)
Method / contextdesign, sample, setting (so you can weight credibility)
Finding / claimdirection + magnitude or the conceptual move
Tensionwhich 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-cites>
【Coding matrix】construct/theory/method/finding/tension rows ready? Y/N
【Coverage risks】<any author/stream an omission referee could name>
【Next skill】→ amann-organizing-framework (impose the integrative spine on the matrix)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する