amann-editor-strategy
Use when working with the Associate Editor and Editor of an Academy of Management Annals (Annals) review — scope alignment after a proposal is invited, what review-article referees evaluate, and revision expectations. Plans the interaction; it does not run the portal preflight (amann-submission) or draft the response letter (amann-revision).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-editor-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Editor & Referee Strategy for a Review (amann-editor-strategy) ## When to trigger - A proposal was invited and you are aligning the full review's scope with the editor - You want to anticipate what Annals referees of a *review* push on (different from a paper) - The editor has asked you to expand, cut, sharpen the framework, or rebalance coverage - You are calibrating revision depth and the twice-yearly cadence ## The editor relationship at Annals is unusually direct Annals' process makes the editor your central partner — more than at most journals. The proposal is reviewed double-blind by the Associate Editors, but once invited, the **full review forgoes double-blind and is developed primarily with the Associate Editor and Editor** (检索于 2026-06；以官网为准). You are effectively co-developing the review with an expert editor who already endorsed the idea. Use that: - **The proposal *is* the scope contract.** The four headings you committed to (Focus / Related reviews / Review scope and process / New insights) define what was invited. Departing from them silently is the fastest way to lose editor confidence — renegotiate explicitly if the literature pushes you elsewhere. - **Lead with t
- When to trigger
- The editor relationship at Annals is unusually direct
- How review differs for a review article
- Checklist
- Anti-patterns
- Output format
What does the amann-editor-strategy skill do?
Use when working with the Associate Editor and Editor of an Academy of Management Annals (Annals) review — scope alignment after a proposal is invited, what review-article referees evaluate, and revision expectations. Plans the interaction; it does not run the portal preflight (amann-submission) or draft the response letter (amann-revision).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-editor-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.