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 aos-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for an Accounting, Organizations and Society (AOS) manuscript. Routes — it does not replace — the specialized skills.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This is the router. It never does the stage work itself; its only job is to name the one aos- skill you should open right now*.
Default target: Accounting, Organizations and Society (AOS) — the flagship interdisciplinary accounting journal, launched in 1976 by Anthony Hopwood and published by Elsevier (ISSN 0361-3682). AOS exists to study accounting as a social, organizational, behavioral and institutional phenomenon, not merely as an input to security prices. Its pages mix qualitative field studies, experimental/behavioral work, surveys, historical and critical scholarship, and archival designs that carry genuine organizational or social theorizing. What AOS is not is a capital-markets outlet: a JAR/JAE/TAR-style archival-financial-economics paper with no social or organizational theory is the journal's canonical desk reject. Every routing decision below therefore starts from which intellectual tradition your paper works in, because the rigor bar, exemplars, and reviewer pool differ sharply between a Bourdieusian field study and a judgment-and-decision-making experiment.
Current masthead (verified 2026-07-16): joint Editors-in-Chief Marcia Annisette (Schulich School of Business), Martin Messner (University of Innsbruck), and Hun-Tong Tan (Nanyang Technological University), supported by a large interdisciplinary editorial board. Submissions run through Editorial Manager (editorialmanager.com/AOS) under double-anonymized review. Editors and portal details change — re-check the official Elsevier/ScienceDirect pages before relying on any of this.
| Current symptom | Next skill |
|---|---|
| Unsure the question is about accounting's organizational/social life at all | aos-topic-selection |
| Data exist but no theoretical lens (or the lens is decorative) | aos-theory-development |
| Front end lists citations without joining an AOS conversation | aos-literature-positioning |
| Field access, case selection, experiment design, or ethics unsettled | aos-methods |
| Material collected; coding, analysis, or statistical treatment unclear | aos-data-analysis |
| Findings exist but the theoretical "so what" is thin | aos-contribution-framing |
| Exhibits (data-structure tables, cell means, figures) weak or absent | aos-tables-figures |
| Prose reads like a hypothesis-mill or buries the argument | aos-writing-style |
| Ready for Editorial Manager; need the preflight | aos-submission |
| Want to understand how AOS editors and reviewers will treat the paper | aos-review-process |
| Revise-and-resubmit received; must plan the revision and letter | aos-rebuttal |
aos-topic-selection — confirm the question belongs at the accounting–organization–society intersectionaos-theory-development — commit to a theoretical tradition and make it do real workaos-literature-positioning — enter a live AOS conversation (the journal has 50 years of its own canon)aos-methods — design the field study / experiment / survey / historical inquiry, with ethics settled earlyaos-data-analysis — code, analyze, or estimate to the standard of your traditionaos-contribution-framing — state what the paper changes in how we understand accounting's social lifeaos-tables-figures — build exhibits that carry evidence, not decorationaos-writing-style — polish the argumentative, theory-carrying prose AOS expectsaos-submission — Editorial Manager preflight (anonymized files, declarations, title page)aos-review-process — calibrate for triage by the joint EiCs and interdisciplinary refereesaos-rebuttal — after an R&R, revise substantively, then draft the responseSteps 7–8 are polish. Touching them while the theoretical lens or the empirical design is still moving wastes the work twice.
aos-theory-development, not more fieldworkaos-contribution-framingaos-topic-selection (probably not, unless the theorizing is social/institutional)aos-literature-positioningaos-submissionaos-review-process then aos-rebuttalThe tradition row governs everything downstream — a field study and an experiment share almost no stage-level standards at AOS. Set it first; then the top unfinished stage names the next skill.
AOS MANUSCRIPT — stage tracker
question : [one sentence: which social/organizational aspect of accounting?]
tradition : qualitative-field / experimental-behavioral / survey /
historical-critical / archival-with-social-theory
target : AOS (vs MAR / AAAJ / CPA / CAR / BRIA) fit=[yes/borderline/no]
stage status next skill
-------------------------------- ------------ ---------------------------
scope & tradition [done] aos-topic-selection
theoretical lens [in-progress] aos-theory-development
conversation entry [todo] aos-literature-positioning
design, access & ethics [todo] aos-methods
coding / analysis / estimation [todo] aos-data-analysis
theoretical contribution [todo] aos-contribution-framing
exhibits [todo] aos-tables-figures (late)
prose [todo] aos-writing-style (late)
Editorial Manager preflight [todo] aos-submission
decision / R&R [—] aos-review-process → aos-rebuttal
rule: the theoretical lens and the design must both be settled
before any (late) row is touched.
aos-writing-style while the paper still has no theoretical argument to express.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。