respol-theory-development
GitHub用于为《Research Policy》稿件构建创新理论框架,解决实证强但理论贡献弱的问题。通过明确因果链条(前因、机制、结果、边界)和跨学科视角,提升论文的理论深度与接受度。
触发场景
安装
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill respol-theory-development -g -y
SKILL.md
Frontmatter
{
"name": "respol-theory-development",
"description": "Use when the conceptual argument is the bottleneck for a Research Policy (RP) manuscript — building an innovation-studies mechanism or framework that an interdisciplinary readership will accept as a contribution. Builds the theory; it does not run the analysis (respol-data-analysis) or write the final contribution paragraph (respol-contribution-framing)."
}
Theory Development (respol-theory-development)
When to trigger
- The empirics are solid but the paper "just measures something" with no innovation-theory advance
- A referee says "the contribution is empirical only" or "what do we learn about innovation we didn't know?"
- The argument leans on one borrowed framework (absorptive capacity, NIS, open innovation) by name only
- A qualitative/case study has rich data but no crisp constructs or propositions yet
- The mechanism linking the innovation cause to the innovation outcome is implicit or hand-waved
The Research Policy theory bar
RP is interdisciplinary, so "theory" is pluralist: it can be economic (incentives, market/coordination failures, appropriability), managerial/organizational (capabilities, search, recombination, governance of R&D), or evolutionary/STS (selection, path dependence, socio-technical regimes, the social shaping of technology). What RP will not accept is atheoretical measurement. The contribution must change how an innovation-studies reader understands a mechanism, an institution, or a system — and the argument must be legible across disciplines, not buried in one field's jargon.
Because RP carries the SPRU/Freeman-Nelson-Pavitt tradition, system- and institution-level reasoning is valued: tie firm- or patent-level findings up to how the innovation system works (incentives, linkages, knowledge flows, policy) rather than stopping at a coefficient.
Building the argument (the innovation-mechanism chain)
For the focal claim, make each link explicit:
- Antecedent — the innovation cause (a policy, an institutional arrangement, a knowledge source, an organizational practice) and why it bites here.
- Mechanism — the innovation process it triggers: knowledge recombination, spillover/absorption, appropriability shift, selection pressure, signaling, coordination of complementary actors. Name the tradition and the process verb (recombines, diffuses, appropriates, selects, legitimates).
- Outcome — the innovation object affected (invention, diffusion rate, entry, productivity of R&D, direction of search), defined at a stated level (inventor, firm, region, sector, system).
- Boundary / system context — the institutional or sectoral conditions under which the mechanism strengthens, weakens, or reverses (e.g., appropriability regime, technological opportunity, absorptive capacity of the receiving unit).
State the level of analysis and keep the theory at the level where the mechanism operates; flag cross-level claims (inventor → region) as such.
Adapting by tradition
- Economic frame: identify the market/coordination failure the innovation policy or institution addresses; predict the sign and the welfare/efficiency logic.
- Managerial/organizational frame: theorize the capability or search process; specify what the firm does differently and why it yields innovation.
- Evolutionary/STS frame: specify variation-selection-retention or the socio-technical configuration; avoid post-hoc storytelling — make the proposition falsifiable.
- Theory-building (qualitative): do not force a priori hypotheses; build a grounded model with emergent propositions and explicit constructs, and argue the theoretical generalization (not statistical) your cases support.
Checklist
- The paper advances an innovation mechanism/framework, not just a measurement
- The driving tradition (economic / managerial / evolutionary-STS) is named and its logic used, not just cited
- Firm/patent-level findings are connected up to the innovation-system or policy level
- Level of analysis is stated and consistent across argument and design
- Boundary/system conditions are theorized, not just listed
- For qualitative work, constructs and propositions are crisp and generalizable theoretically
- At least one rival explanation is named and engaged
Anti-patterns
- Atheoretical measurement: a clean indicator with no claim about how innovation works
- Framework name-dropping: invoking NIS / absorptive capacity / open innovation without using its actual logic
- Stopping at the coefficient: never connecting the estimate up to the innovation system or policy
- Single-discipline opacity: an argument only one field can read, in an interdisciplinary journal
- HARKing in disguise: propositions reverse-engineered from the results in a "build" paper
- Boundary as decoration: a moderator with no theoretical account of why the mechanism shifts
Output format
【Journal】Research Policy
【Skill】respol-theory-development
【Tradition】economic / managerial-organizational / evolutionary-STS / theory-building
【Mechanism chain】antecedent → innovation process → outcome (level)
【System/policy link】how it scales up to the innovation system
【Boundary conditions】where it strengthens / weakens / reverses
【Rival explanation addressed】...
【Verdict】pass / revise / reroute
【Next skill】respol-literature-positioning
版本历史
- 1839142 当前 2026-07-05 14:19


