MCPInstall

paper-planning

Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).

Installs
418
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/evoscientist/evoskills --skill paper-planning
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads paper-planning automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Paper Planning

A structured approach to planning academic papers before writing begins. Covers four key activities: Story design, Experiment planning, Figure design, and Timeline management.

When to Use This Skill

If you don't yet have an idea, use the research-ideation skill first to find a problem and design a solution.

  • User wants to plan a paper before writing
  • User asks about structuring a paper's story or contributions
  • User needs to plan experiments (comparisons, ablations)
  • User wants to design pipeline figures or teaser figures
  • User asks about writing timelines or submission schedules

Planning Overview

Paper planning follows four steps, ideally completed before writing begins:

Step 1: Story Design     → What is the narrative? What are the contributions?
Step 2: Experiment Plan   → What experiments prove our claims?
Step 3: Figure Design     → How do we visually communicate the method?
Step 4: Timeline          → When does each section get written?

Counterintuitive Planning First

Prioritize these counterintuitive rules before regular planning:

  1. Write your rejection letter first: Draft the top-5 likely rejection comments ("limited novelty", "missing baseline", "not robust", etc.), then plan experiments that directly preempt each one.
  2. Narrow claim before broad claim: Define the smallest defensible core claim first. Expand only after evidence is strong. Over-broad claims fail review more often than narrow strong claims.
  3. Design ablations before polishing method text: If a module cannot be ablated cleanly, its contribution claim is weak.
  4. Allocate compute to stress tests, not only benchmarks: A single convincing stress-test figure often contributes more than multiple small benchmark gains.
  5. Plan a fallback narrative now: If SOTA gain is marginal, predefine a secondary value proposition (efficiency, robustness, fewer assumptions, wider applicability).

See references/counterintuitive-planning.md


Step 1: Story Design

The "story" is the logical narrative that connects the problem, insight, method, and results.

Reverse Engineering the Story

Work backwards to build the story:

  1. What is the technical problem? — The specific challenge that existing methods cannot solve well
  2. What are our contributions? — The concrete technical novelties
  3. What are the benefits and new insights? — What advantages does our approach provide?
  4. How do we lead into the challenge? — How to frame the task and previous methods to naturally arrive at the challenge

Then write forward: Task → Previous methods → Challenge → Our contributions → Advantages

Core Elements to Define

Before writing any section, clearly articulate:

ElementQuestionExample
TaskWhat problem does this paper address?"Real-time 3D scene reconstruction"
ChallengeWhy can't existing methods solve it well?"Cannot handle dynamic objects efficiently"
InsightWhat key observation drives our approach?"Motion patterns are temporally sparse"
ContributionWhat do we propose?"Sparse temporal attention for dynamic regions"
AdvantageWhy is our approach better?"Reduces computation while preserving quality"

Starting Point: Pipeline Figure Sketch

Start by drawing a pipeline figure sketch. This forces you to clarify the overall method before writing.

The pipeline figure sketch serves as the paper's visual backbone:

  • Draw it before writing anything
  • It reveals whether the method is clear enough to explain
  • It identifies the novel modules vs. standard components
  • It determines subsection structure for the Method section

See references/story-design.md


Step 2: Experiment Planning

Plan experiments before writing to avoid discovering gaps late.

Two Categories of Experiments

Comparison Experiments — Prove our method is better:

  • Which baseline methods to compare against?
  • Which datasets and metrics?
  • What is the evaluation protocol?

Ablation Studies — Prove each module is effective:

  • Part 1: One big table showing impact of core contributions
  • Part 2: Several small tables for design choices and hyperparameters

Planning Checklist

  • List all comparison baselines (recent, relevant, SOTA)
  • Define evaluation metrics (standard for the task)
  • Identify datasets (standard benchmarks + challenging demos)
  • List ablation configurations (remove each core component)
  • Plan design-choice tables (hyperparameters, input quality, alternatives)
  • Plan demo scenarios (challenging data to showcase upper limit)

See references/experiment-planning.md

Experiment Plan Template

Use the template at assets/experiment-plan-template.md to organize your experiment plan.


Step 3: Figure Design

The pipeline figure is for highlighting novelty, not for making readers understand. The Method text is what makes readers understand.

Pipeline Figure Principles

  • Highlight novelty: The pipeline figure showcases what is new, not just the workflow
  • Differentiate from prior work: The figure must look different from previous methods
  • Novel modules stand out: If the overall pipeline is standard, zoom in on novel modules
  • Focus on clarity of the novel parts; standard components can be simplified

Teaser Figure

The teaser (usually Figure 1) shows the key result at a glance:

  • Place it at the top of the first page
  • Should be immediately compelling
  • Reference it from the Introduction

Visual Quality Matters

Visual polish directly influences review outcomes. See references/figure-design.md for the full visual quality guide (pipeline figures, tables, typography)


Step 4: Timeline

4-Week Countdown

Start writing at least 1 month before the deadline.

WeekTasks
4 weeks before1. Organize story (core contribution, module motivations). 2. List comparison experiments and ablation studies. 3. Write Introduction first draft.
3 weeks before1. Finalize the pipeline figure sketch. 2. Write Method first draft (use \todo{} for unsettled details). Deadline: give Introduction + Method draft to advisor.
2 weeks beforeWrite first drafts of Experiments, Abstract, Related Work.
Last weekRevise paper, polish pipeline figure and teaser, run demos.

Critical: By the end of Week 3, you must send the Introduction and Method drafts to your advisor — otherwise the advisor likely will not have enough time to finish reviewing the paper.

See references/timeline-4week.md for the detailed schedule and progress tracking template.


Handoff to Writing

When planning is complete, pass these artifacts to paper-writing:

ArtifactSource StepUsed By
Story summary (task → challenge → insight → contribution → advantage)Step 1Introduction
Module Motivation Mapping tableStep 1Method subsections
Experiment plan (comparisons + ablations + demos)Step 2Experiments section
Pipeline figure sketchStep 1 / Step 3Method overview + Figure 2
Claim-to-experiment mappingStep 2Abstract, Introduction, Experiments
Fallback narrative (if planned)Counterintuitive Rule 5Introduction / Conclusion pivot
Rejection-risk tableCounterintuitive Rule 1Self-review prioritization

Reference Navigation

TopicReference FileWhen to Use
Story designstory-design.mdStarting a new paper
Experiment planningexperiment-planning.mdBefore running experiments
Timelinetimeline-4week.mdSetting up a writing schedule
Figure designfigure-design.mdDesigning pipeline/teaser figures
Experiment plan templateexperiment-plan-template.mdCreating a structured experiment plan
Counterintuitive strategycounterintuitive-planning.mdIncreasing acceptance odds with non-obvious planning choices

Handoff to Presentation

If preparing a conference talk or slide deck, the academic-slides skill guides slide creation from your planning artifacts — including translating your story design and pipeline figure into presentation structure.

FAQ

What does the paper-planning skill do?

Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).

How do I install paper-planning?

Run npx skills add https://github.com/evoscientist/evoskills --skill paper-planning in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/paper-planning/ (personal) or .claude/skills/paper-planning/ (project).

Which AI agents can use paper-planning?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is paper-planning safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains paper-planning?

It is published by evoscientist in evoscientist/evoskills. It has 418 recorded installs.

More from evoscientist/evoskills

View all →

paper-review

evoscientist/evoskills

Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: three passes (adversarial deep read; 5-aspect checklist — contribution sufficiency, writing clarity, results quality, testing completeness, method design; mechanical consistency scans and experimental protocol audit of data flow, assumptions, leakage), counterintuitive protocol (reject-first simulation, delete unsupported claims, score trust, promote limitations, attack novelty), reverse-outlining, and figure/table quality checks. Use when: user wants to self-review or self-check their own paper draft before submission, stress-test their claims, prepare for reviewer criticism, or mentions 'self-review', 'check my draft', 'is my paper ready'. Do NOT use for writing a peer review of someone else's paper, and do NOT use after receiving actual reviews (use paper-rebuttal instead). Also runs as a background expert: dispatch it async with a draft path and it reviews end-to-end while

paper-writing

evoscientist/evoskills

Guides writing academic papers section by section using an 11-step workflow with LaTeX templates and counterintuitive writing tactics. Covers Abstract, Introduction, Method, Experiments, Related Work, Conclusion, and Supplementary. Use when: user asks to write or draft a paper section, needs LaTeX templates, wants to improve academic writing quality, optimize novelty framing, or mentions 'write introduction', 'draft method', 'paper writing'. Do NOT use for pre-submission review (use paper-review), experiment execution (use experiment-pipeline), or paper planning/story design (use paper-planning).

research-ideation

evoscientist/evoskills

End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update evo-memory (IDE) → user selects direction → expand into manuscript-quality proposal. Use when: user wants to find a research direction, brainstorm ideas, evaluate idea novelty, design a novel solution, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use paper-navigator), literature survey reports (use research-survey), or planning a paper (use paper-planning).

academic-slides

evoscientist/evoskills

Use this skill for creating or refining an academic slide deck and the talk built around it: structuring a conference talk, thesis defense, lab meeting, or paper-to-slides deck; deciding the narrative arc and slide breakdown; improving slide design and visual hierarchy; planning rehearsal, timing, Q&A, and backup slides; or generating the .pptx. Reach for it when the user is shaping the presentation itself. Do not use for writing the paper, producing standalone speaker notes/scripts/transcripts, making posters, creating isolated figures/charts outside a slide deck, or building non-academic presentations.

Docs & Writing482 installs

paper-rebuttal

evoscientist/evoskills

Open the skill to read its SKILL.md instructions.

experiment-pipeline

evoscientist/evoskills

Open the skill to read its SKILL.md instructions.

390 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.