Use when positioning a Public Administration Review (PAR) manuscript against the literature so it reads as a field-wide contribution that also informs practice. PAR readers span public management, governance, and the practitioner community, so the paper must engage the core PA debates and not just one niche. Stakes the contribution; it does not write the lit review.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-literature-positioning --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pubar Literature Positioning?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-pubar-literature-positioning)More formats (shields.io, HTML) on the badges page.
---
name: pubar-literature-positioning
description: Use when positioning a Public Administration Review (PAR) manuscript against the literature so it reads as a field-wide contribution that also informs practice. PAR readers span public management, governance, and the practitioner community, so the paper must engage the core PA debates and not just one niche. Stakes the contribution; it does not write the lit review.
---
# Literature Positioning (pubar-literature-positioning)
PAR is read across public management *and* by reflective practitioners, so positioning must place the
paper where a **general public-administration audience** sees both the scholarly gap and the practical
stake. A "literature dump" that engages only one niche reads as off-fit for the field's flagship.
## When to trigger
- Drafting or revising the introduction and the "contribution" paragraph
- A reviewer said you "missed core PA work" or "don't engage the debate"
- Your niche literature is solid but the paper doesn't connect to broader public management
- You need to distinguish your contribution from the closest prior PAR/JPART papers
## How PAR wants the literature engaged
1. **Engage the live PA debate, not a pile of citations.** Identify the open question your paper
speaks to (e.g., does performance measurement improve outcomes or distort behavior; what makes
collaborative governance work; how does red tape affect public service motivation).
2. **Two audiences at once.** Satisfy PA scholars (you know the frontier) *and* the field's
practice-bridging mission (why a manager would care). The intro should make a budgeting scholar
care about a personnel paper and vice versa.
3. **Name the gap precisely.** Not "little is known" — say what is contested, mismeasured,
under-theorized, or untested in public management, and why resolving it advances the field.
4. **Position the contribution as a move in the debate.** "Prior PA work argues X via mechanism M; we
show M fails / is conditional on context C / is better explained by M′."
5. **Pre-empt the obvious objection.** PAR reviewers are public-management experts; name the strongest
rival account and say how your design adjudicates it (hand off to `pubar-research-design`).
## Cross-subfield engagement (a distinctive PAR demand)
| If your paper is… | also engage… |
|-------------------|--------------|
| a performance-management study | the accountability, goal-ambiguity, and gaming literatures |
| a public-HR / PSM study | the motivation, leadership, and bureaucratic-behavior work it bears on |
| a collaborative-governance case | the general theory of networks, coordination, and co-production |
| a budgeting / finance study | the implementation and managerial-discretion literatures it informs |
## Don't drift to a sibling literature
PAR is not JPART (theory-driven), Governance (comparative institutions), or JPAM (policy analysis). If
your positioning cites only formal-theory work with no managerial payoff, you are writing a JPART
intro. If it is a cost-benefit framing, you are writing a JPAM intro. Re-anchor to public-management
practice.
## Anti-patterns
- A "literature dump" with no organizing PA debate
- Engaging only one niche (a top PAR rejection reason for the field's flagship)
- Strawmanning prior work, or hiding the closest competitor paper
- Self-citation that breaks anonymity (PAR is double-blind — see `pubar-submission`)
- Claiming "first to study" when the contribution is incremental
## Output format
```
【Debate】the live PA disagreement / open question
【Key works】the 3-6 that define it (incl. cross-subfield PA)
【Gap】what is contested / mismeasured / untested
【Move】how this paper changes the debate
【Practitioner stake】why the resolved gap matters for management
【Strongest rival】and how the design will adjudicate it
【Next】pubar-theory-building
```
## Referee-pushback patterns and the PAR fix
- *"The contribution is niche, not field-level PA."* → Recast the gap as a live debate the whole field
recognizes, and add the 3–6 cross-subfield works that define it.
- *"You missed core PA work / don't engage the debate."* → Map the live disagreement, then cite the
works that *constitute* it, not a citation pile.
- *"This reads like JPART/JPAM."* → Re-anchor positioning to public-management practice and the
Evidence-for-Practice stake, not pure theory or policy choice.
- *"Closest competitor is hidden."* → Name the nearest prior paper and state exactly what your move
changes (mechanism fails / is conditional / is better explained).
## Calibration anchors (hedged)
- PAR's premium is **field-wide significance plus practice relevance**; positioning that satisfies only
one niche is structurally weak even when the within-niche contribution is real.
- The bridge across literatures (e.g., linking budgeting to motivation) is itself a positioning asset
at a generalist PA flagship.
- "Engage the relevant literature" wording and desk-screen criteria can change — confirm the current
guidance on the journal's submission page before relying on it (检索于 2026-06;以官网为准).
## Supplementary resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — scope and contribution expectations
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!