Agent skill · Code Review & Quality

amann-review-process

Use when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal review, the editor-only full-review development, and timelines. Explains the process; it does not write the proposal (amann-proposal-framing) or run the portal preflight (amann-submission).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Academy-of-Management-Annals-Skills/skills/amann-review-process/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# The Annals Review Process (amann-review-process) ## When to trigger - You are deciding whether to start now or wait for the next deadline - You need to understand who reviews what, when, and how blinding changes between stages - You are planning a realistic timeline from proposal to published review - A coauthor assumes Annals works like a normal journal (it does not) ## The two-step process is the defining feature Annals does not accept full reviews cold. Intake is a **gated, two-step process** (检索于 2026-06;以官网为准): | Stage | What happens | Blinding & reviewers | Output | |-------|--------------|----------------------|--------| | **1. Proposal** | Submit a ≤5-page proposal (four headings) at a deadline | **Double-blind**, reviewed by the **Associate Editors** | Invitation to develop the full review, or decline | | **2. Invited full review** | Develop the ~50-page review with editorial guidance | **Forgoes double-blind**; read by the **Associate Editor and Editor** | Conditional acceptance / revisions / decline | The consequences are large: most of the *gatekeeping* happens at the lightweight proposal stage, and most of the *development* happens collaboratively with an editor who

What's inside
Steps it walks through
  1. When to trigger
  2. The two-step process is the defining feature
  3. The cadence
  4. Planning the timeline
  5. Checklist
  6. Anti-patterns
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the amann-review-process skill do?

Use when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal review, the editor-only full-review development, and timelines. Explains the process; it does not write the proposal (amann-proposal-framing) or run the portal preflight (amann-submission).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process --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.

Keep going