aaai-artifact-evaluati…
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance…
Use when writing the short proposal that gates an Academy of Management Annals (Annals) review — the ≤5-page, four-heading proposal submitted under the twice-yearly deadlines before any full review is invited. Builds the proposal; it does not gather the literature
Claude Code
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing --agent claude-code
Codex
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a codex -y
Cursor
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a cursor -y
Gemini CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a gemini-cli -y
GitHub Copilot
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a github-copilot -y
OpenCode
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a opencode -y
Windsurf
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-proposal-framing -a windsurf -y
name: amann-proposal-framing description: Use when writing the short proposal that gates an Academy of Management Annals (Annals) review — the ≤5-page, four-heading proposal submitted under the twice-yearly deadlines before any full review is invited. Builds the proposal; it does not gather the literature (amann-literature-synthesis) or run the portal preflight (amann-submission).
Annals uses a **two-step, proposal-first process**. You do **not** submit a full review cold; you submit a short proposal, and only an **accepted proposal is invited** to develop into a full article.
1. **Focus of the review** — the literature and the animating problem. 2. **Related reviews** — what reviews already exist and why yours is *not* redundant. 3. **Review scope and process** — boundaries, inclusion logic, how you will gather and synthesize the corpus. 4. **New insights** — the integrative contribution, the "attitude," and the agenda the review will produce.
> The ≤5-page proposal is the single most consequential document in the Annals lifecycle: it is the gate. A strong proposal earns an invitation before you sink months into reading and drafting; a weak one ends the project regardless of how good the eventual review would have been. Treat it as a high-stakes argument, not an outline.
| Heading | What it must do | Common failure | |---------|-----------------|----------------| | **Focus of the review** | Name the literature and the *problem with the field* (from `amann-topic-selection`), not just the topic | A topic label ("a review of X") with no problem | | **Related reviews** | Show command of prior reviews and stake the *delta* — what yours does that none did | Claiming "no review exists" instead of differentiating from the ones that do | | **Review scope and process** | State boundaries, inclusion/exclusion logic, databases, and the synthesis method (narrative / systematic / bibliometric) | Vague "we will read the literature" with no transparent process | | **New insights** | Lead with the *integrative framework* and the agenda — the new way of seeing the field, with attitude | A promise of "comprehensive coverage" and no new organizing idea |
The center of gravity is **New insights**: Associate Editors are deciding whether this review will *reorganize* the field, not whether it will summarize it. A proposal that nails coverage but offers no framework is the most common proposal-stage reject.
【Focus of the review】<literature + animating problem, one sentence> 【Related reviews】<existing reviews + the delta yours provides> 【Review scope and process】<boundaries / inclusion logic / databases / synthesis method> 【New insights】<integrative framework + agenda + the critical attitude> 【Length check】≤5pp single-spaced, 1-in margins, 12pt (refs/visuals excluded)? Y/N 【Deadline】targeting April 1 / October 1? <which> 【Balance note】<how author's own work is handled, if a contributor> 【Open verifications】portal / CV / specifics re-confirmed on official page? Y/N 【Next skill】→ amann-literature-synthesis (begin systematic reading) after invitation
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance…
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL…
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits,…
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical…
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and…
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and…
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to…