Agent Skills
› brycewang-stanford/Awesome-Journal-Skills
› amann-revision
amann-revision
GitHub针对管理学会公报（Annals）的提案或全文审稿意见，起草逐点回复信及修订计划。涵盖框架强化、态度立场、覆盖缺口、平衡性及准确性等反馈类型的应对策略，区分提案阶段与全文评审阶段的处理差异。
Trigger Scenarios
收到Annals提案决定信（如修改后重投）
收到全文审稿人意见（通常为大修）
审稿人指出缺乏理论框架、文献罗列或覆盖不全
需要撰写综述文章的逐点回复信
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -g -y
SKILL.md
Frontmatter
{
"name": "amann-revision",
"description": "Use when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework\/attitude asks, coverage gaps, balance complaints, and accessibility. Drafts the response letter and revision plan; it does not run the portal preflight (amann-submission) or redesign the framework from scratch (amann-organizing-framework)."
}
Revision & Response for a Review (amann-revision)
When to trigger
- A proposal decision letter arrived (invited / revise-and-resubmit / declined)
- A full-review referee letter arrived (major revision is the norm for a long review)
- Referees flagged "no real framework," missing streams, imbalance, or "reads like a list"
- You need a point-by-point response letter for a review article, not a primary paper
First: which letter is this?
Annals' two-step process produces two kinds of feedback, and they call for different moves:
- Proposal-stage feedback (double-blind, from the Associate Editors). The decision is mainly about fit and promise: is the literature Annals-scale, and is there a genuinely new framework under "New insights"? A revise-and-resubmit here usually means sharpen the contribution before the full review is invited — route back through
amann-topic-selection/amann-organizing-framework/amann-proposal-framing. - Full-review feedback (editor-only: Associate Editor and Editor). The review is being developed; feedback is about execution — framework strength, coverage, balance, attitude, accessibility. This is the classic point-by-point revision below.
Categories of full-review feedback (and how to answer each)
Triage every point into one bucket:
| Feedback type | Typical phrasing | Response move |
|---|---|---|
| Framework / contribution | "this is an annotated bibliography" / "where is the integration?" | strengthen or make explicit the spine (amann-organizing-framework); do not just reorder — this is the acceptance bar |
| Attitude / agenda | "this is descriptive; take a position" / "the agenda is generic" | add the critical position and a framework-tied agenda (amann-writing-style) |
| Coverage gap | "you omit the X stream / author Y" | almost always concede and integrate; place the work in the right cell; re-run saturation (amann-literature-synthesis) |
| Balance / fairness | "this slights school Z / over-cites the author" | steelman the slighted side; re-audit self-citation (amann-evidence-standards) |
| Appraisal accuracy | "you mischaracterize study W" | correct it precisely — reviewed authors often referee |
| Scope | "too broad / too narrow" | renegotiate with the editor (amann-editor-strategy); rescope deliberately, not by random cuts |
Writing the response letter
- Point-by-point, quote-then-respond. Reproduce each comment, then state the change and where it lives (section/page/table/figure).
- Framework asks are existential — answer them first. "No real framework" is a reject reason at Annals; a stronger or more explicit spine, not reordered paragraphs, is the required answer.
- Coverage asks: concede gracefully and integrate. A missing stream is a real defect in a review-of-the-field; adding it strengthens the article. Resist defensiveness.
- Balance asks: show the steelman. Demonstrate the revised text states the other side at its strongest.
- Disagree rarely and respectfully. If an ask would break the framework or expand scope unfinishably, explain the trade-off and propose an alternative, ideally pre-cleared with the editor.
- Keep the editor central. Because the full review is developed with the AE and Editor, route scope conflicts and incompatible asks to them rather than trying to satisfy everyone.
- Track every addition's ripple. Adding a stream can shift the review's center of gravity; after each integration, re-check that the framework cells, the synthesis tables, and the balance audit still hold.
Checklist
- Identified whether the letter is proposal-stage (fit/promise) or full-review (execution)
- Every comment triaged (framework / attitude / coverage / balance / appraisal / scope)
- "No framework" / "annotated bibliography" answered with a stronger explicit spine, not reordering
- "Descriptive" answered by adding a critical position + framework-tied agenda
- Coverage gaps conceded and integrated into the right cell; saturation re-run
- Balance complaints answered by demonstrable steelmanning + self-citation re-audit
- Mischaracterizations corrected precisely (reviewed authors may be the referees)
- Scope conflicts routed to the editor for adjudication
- Point-by-point letter: quote-then-respond, with section/page/table locations
- Framework, coverage, and balance re-audited after all additions
Anti-patterns
- "Fixing" a no-framework critique by shuffling paragraphs without strengthening the spine
- Answering a "be more provocative" ask with the same neutral prose
- Defending an omission rather than adding the missing stream (a review gap is a real defect)
- Answering a balance complaint with assertions of fairness instead of revised, steelmanned text
- Mischaracterizing or dismissing a reviewed author who is likely your referee
- Bloating scope to satisfy every "also cover…" until the review no longer finishes
Output format
【Letter type】proposal-stage (fit/promise) / full-review (execution)
【Triage】each comment bucketed (framework/attitude/coverage/balance/appraisal/scope)? Y/N
【Framework asks】spine strengthened/made explicit (not reordered)? Y/N
【Attitude/agenda】critical position + framework-tied agenda added? Y/N
【Coverage gaps】conceded + integrated into cells; saturation re-run? Y/N
【Balance】steelman shown in revised text; self-citation re-audited? Y/N
【Scope conflicts】routed to editor? Y/N
【Letter】point-by-point, quote-then-respond, with locations? Y/N
【Next skill】→ amann-submission (re-preflight the revised proposal or review)
Version History
- 1839142 Current 2026-07-05 12:13
