From annual-review-of-sociology-skills
Designs an analytical taxonomy or organizing framework for an Annual Review of Sociology literature review, turning a reading list into a structured argument.
How this skill is triggered — by the user, by Claude, or both
Slash command
/annual-review-of-sociology-skills:arsoc-organizing-frameworkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The evidence matrix is built but the draft would read like a list of studies
The single most-cited reason ARSoc reviews disappoint is that they are annotated bibliographies: study-after-study summaries with no organizing idea. A great ARSoc review imposes a structure the subfield did not have — a taxonomy, a unifying mechanism, a sequence of questions, or a simple analytic model — that makes scattered work legible to a sociologist from another area. The framework is the contribution; the citations are the evidence. Choose the spine deliberately:
| Spine type | Organizes the subfield by | Best when |
|---|---|---|
| Taxonomy | mutually-exclusive categories of mechanism / theoretical approach | the area is fragmented into incommensurable camps |
| Mechanism / process | the causal or social process linking inputs to outcomes | results disagree because they tap different stages of one process |
| Levels of analysis | micro / meso / macro, or individual / organizational / institutional | the field spans levels and the lesson is how they connect |
| Question sequence | a logical chain of sub-questions | the area has a natural "first we must know X, then Y" order |
| Paradigm / debate | rival theoretical traditions and what divides them | the contest of perspectives is itself the subfield's structure |
Pick one primary spine; a second axis can be a within-section ordering, but a review with two competing spines reads as two reviews.
Stress-test by trying to place 5 hard cases (studies that resist categorization). If three of them have no home, the spine is wrong — redesign before drafting.
The framework is also what lets you be selective without being incomplete: once each cell is defined, confirmatory studies can be cited in clusters within their cell while the prose discusses only the cell-defining work. A review without a spine cannot do this — it must either summarize everything (bloat) or omit silently (gaps). Design the spine before you decide what to foreground, and note which cells are thin — those become the research agenda the ARSoc voice closes on.
【Spine type】taxonomy / mechanism / levels-of-analysis / question-sequence / paradigm-debate
【Argument about the subfield】"<one sentence the review makes>"
【Categories】<the cells / sub-questions, each MECE>
【Reconciliation】<which contradiction the framework explains>
【Open questions】<empty/thin cells surfaced as gaps for the forward agenda>
【Hard-case test】5 awkward studies each placed? Y/N
【Next step】→ arsoc-comprehensiveness-and-balance (fill cells fairly + even-handedly)
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin annual-review-of-sociology-skillsImposes an analytical structure or taxonomy on economics literature for Annual Review of Economics reviews, turning a reading list into an argument about the field.
Imposes an analytical structure or taxonomy on psychology literature for Annual Review of Psychology reviews. Selects spine type (taxonomy, process model, etc.) to turn a reading list into a coherent argument.
Designs the organizing framework for Academy of Management Annals reviews, turning scattered papers into a theory-advancing 'new way of seeing' the field.