Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which amann-* sub-skill to invoke next, or when sequencing a comprehensive review article from topic selection through revision for an Academy of Management Annals (Annals) submission. Routes — it does not replace — the specialized skills.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This is the router. It tells you which amann- skill to use at the current stage* of a comprehensive, integrative review article aimed at the Academy of Management Annals (Annals) — the Academy of Management's review-of-the-field journal, published with Taylor & Francis. Annals does not publish original empirical research or stand-alone new theory; it publishes authoritative, theory-advancing reviews that synthesize a management/organization literature. Its mission is "up-to-date, in-depth and integrative reviews of research advances in management," and its house identity is "reviews with an attitude": a review must take a critical, integrative stance and set an agenda, not merely catalog papers (检索于 2026-06;以官网为准).
So the lifecycle is not "design → identify → estimate → defend." It is judge whether a literature is Annals-scale → write the ≤5-page proposal (the gate) → if invited, read the whole literature → impose a novel organizing framework → appraise the evidence even-handedly → build synthesis exhibits → land the Annals voice → develop the full review through the editor-only process. The single binding constraint at every step is the same: does this review create a new way of seeing the field? A review that summarizes accurately but reorganizes nothing is the canonical Annals reject.
Default assumption: unless told otherwise, treat the target as Annals and the artefact as a comprehensive review, not a primary paper. Tells that you are at Annals and not a sibling: the work synthesizes other people's research rather than reporting your own; the first deliverable is a short proposal under a twice-yearly deadline, not a full draft; there is no hypothesis test or dataset of your own — you appraise the studies you cover; the contribution is an integrative map and agenda for a field. If the user has original theory, route to AMR; original data, route to AMJ — say so.
| Current symptom | Next skill |
|---|---|
| Unsure the literature is mature/important/fragmented enough for Annals | amann-topic-selection |
| Need to write the ≤5-page proposal that gates the whole process | amann-proposal-framing |
| Reading is unsystematic; coverage gaps a referee could name are likely | amann-literature-synthesis |
| Draft is a list of papers, not an argument about the field | amann-organizing-framework |
| Appraisal of cumulative evidence / balance across schools feels off | amann-evidence-standards |
| Need who-found-what tables or a framework diagram | amann-tables-figures |
| Prose is descriptive/jargon-laden; the "attitude" and agenda are missing | amann-writing-style |
| Negotiating scope with the editor or anticipating review-article referees | amann-editor-strategy |
| Ready to submit a proposal or invited full review via Manuscript Central | amann-submission |
| Need to understand the two-step proposal→invited-review choreography and timelines | amann-review-process |
| Received a proposal decision or full-review referee letter | amann-revision |
amann-topic-selection — confirm the literature is Annals-scale (mature, important, fragmented, integrable)amann-proposal-framing — write the ≤5-page, four-heading proposal (the gate)amann-literature-synthesis — once invited, read the field systematically to saturationamann-organizing-framework — impose the novel integrative spine (the acceptance bar)amann-evidence-standards — appraise cumulative evidence and balance across schoolsamann-tables-figures — synthesis tables and the signature framework figureamann-writing-style — the authoritative, agenda-setting "attitude" voice (intro + abstract last)amann-editor-strategy — scope negotiation and review-article referee expectationsamann-submission — Manuscript Central preflight (proposal or invited full review)amann-review-process — the proposal→invited-review process and twice-yearly cadenceamann-revision — after the proposal decision or full-review letter
amann-writing-styleis a late polish; do not rewrite the intro before the framework and evidence appraisal settle. The proposal comes early and is the gate — at Annals you cannot submit a full review cold, soamann-proposal-framingprecedes the heavy reading.
A "review" is not one thing; the bottleneck differs by type. Read the archetype, then enter the chain at the right link.
| Archetype | Likely first bottleneck | Enter at |
|---|---|---|
| field-defining integrative review (broad domain) | scope is enormous; needs a new organizing architecture | amann-organizing-framework |
| construct-clarification / reconciliation review | rival definitions and incommensurable measures; needs an integrating logic | amann-organizing-framework |
| cumulative-evidence stock-take (what do we know?) | even-handed appraisal of conflicting findings | amann-evidence-standards |
| emerging / fast-moving domain review | is it mature enough for Annals yet? | amann-topic-selection |
| systematic / bibliometric review | search transparency + turning the corpus into an argument | amann-literature-synthesis |
if proposal_decision_or_referee_letter: -> amann-revision
elif understanding_two_step_process: -> amann-review-process
elif ready_to_submit: -> amann-submission
elif scope_or_referee_anticipation: -> amann-editor-strategy
elif prose_descriptive_no_attitude: -> amann-writing-style
elif need_tables_or_framework_figure: -> amann-tables-figures
elif evidence_appraisal_or_balance_off: -> amann-evidence-standards
elif reads_like_a_list: -> amann-organizing-framework
elif reading_unsystematic: -> amann-literature-synthesis
elif no_proposal_yet: -> amann-proposal-framing
else: -> amann-topic-selection
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.
日本語の概要は準備中です。原文の説明を表示しています。