Contribution Framing & Discussion (amj-contribution-framing)
SkillDev toolsUse when turning results into an explicit theoretical contribution for an Academy of Management Journal (AMJ) manuscript, the "what new theory do we learn?" statement and the discussion section. Frames the contribution and implications; it does not build the original theory (amj-theory-development) or run the analysis (amj-data-analysis).
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Contribution Framing & Discussion (amj-contribution-framing) skill
What this skill tells your AI
The instructions your AI receives, as published by brycewang-stanford/awesome-journal-skills in Academy-of-Management-Journal-Skills/skills/amj-contribution-framing/SKILL.md and read by ahel’s review.
When to trigger
- Results are in but the "so what for theory" is vague or missing
- The discussion restates findings instead of advancing the theory
- A reviewer says the contribution is "incremental," "descriptive," or "unclear"
- You can describe what you found but not what the field now knows that it did not before
- The practical-implications paragraph is generic ("managers should pay attention to X")
The contribution question AMJ asks
AMJ evaluates every paper on three criteria: a strong empirical contribution, a meaningful theoretical contribution, and practical relevance. The empirical contribution must be paired with a theoretical one: what do we now understand about the theory that we did not before? — and the discussion must also speak to why it matters for management practice. A clear, defensible theoretical answer is essential; strong results with no theoretical advance read as a technical report, not an AMJ paper. AMJ's From the Editors tradition frames this as the "so what?" and "who cares?" tests.
Types of theoretical contribution (claim the right one)
| Contribution type | What it does |
|---|---|
| Reveal a new mechanism | Explains why an established effect occurs |
| Establish a boundary | Shows when an effect holds, weakens, or reverses |
| Adjudicate competing theories | Shows which of two rival predictions holds, and why |
| Integrate / bridge | Connects two literatures into a more general account |
| Challenge an assumption | Overturns a taken-for-granted premise (problematization) |
| Introduce/refine a construct | Conceptualizes and validates a new construct that earns its keep |
State explicitly which type(s) you claim; do not gesture vaguely at "contributing to the literature."
Writing the discussion
A strong AMJ discussion typically:
- Restates the core finding in theoretical terms (one short paragraph, no number-dump).
- Theoretical implications — for each, name the literature, state what changes, and how (this is the heart of the section).
- Practical implications — a genuine AMJ criterion, not an afterthought: specific to the phenomenon and grounded in the findings, never boilerplate. (Practical relevance is one of AMJ's three formal acceptance criteria, but it complements rather than substitutes for the theoretical contribution.)
- Limitations — honest, but framed as boundary conditions and future directions, not as fatal flaws.
- Future research — concrete questions the study opens, tied to the mechanism/boundary.
Match the discussion to the front end: the contributions you claim here must be the ones you promised in the introduction. A reviewer will check that the intro's promise and the discussion's delivery line up.
The contribution statement (intro and discussion)
Draft 2–4 explicit contribution sentences and place a version in the introduction and the discussion. Each should be of the form: "We contribute to [literature] by showing [mechanism/boundary/integration], which advances [theory] because [reason]."
Checklist
- The theoretical contribution type is named (mechanism/boundary/adjudication/integration/assumption/construct)
- 2–4 explicit contribution sentences, consistent between intro and discussion
- Discussion advances theory, not just restates results
- Practical implications are specific to the phenomenon and the findings
- Limitations framed as boundary conditions + future directions, not fatal flaws
- Future research questions follow from the mechanism/boundary, not generic
- Intro's promised contribution = discussion's delivered contribution
Anti-patterns
- Restating results as "contribution": "We found A affects B" is a finding, not a contribution.
- Incremental framing: "We extend prior work to a new setting" with no theoretical change.
- Over-claiming: asserting a paradigm shift the single study cannot support.
- Boilerplate practical implications: "managers should be aware of X" untethered from the data.
- Intro/discussion mismatch: promising one contribution, delivering another.
- Limitations as confession: listing flaws without converting them into boundary conditions.
Output format
【Contribution type(s)】mechanism / boundary / adjudication / integration / assumption / construct
【Contribution sentences】1–4, intro + discussion aligned
【Theoretical implications】per literature: what changes and why ...
【Practical implications】specific, grounded ...
【Limitations → boundaries】...
【Future research】concrete, mechanism-tied ...
【Intro↔discussion consistency】yes/no
【Next step】amj-tables-figures, then amj-writing-style
Signals
- GitHub stars
- 1k
- Forks
- 155
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
amj-contribution-framing- Source
- github.com/brycewang-stanford/awesome-journal-skills
github.com/brycewang-stanford/awesome-journal-skills
Related picks
Skill · agricidaniel
The pick for Markdownmarkdown-formatter
Skill · nvidia
The pick for Markdownacademic-paper-composer
Skill · brycewang-stanford
The pick for Academic03-academic-writing
Skill · 24kchengye
The pick for Academicteach
Skill · mattpocock
More in Dev toolsimplement
Skill · mattpocock
More in Dev tools