paper-positioning-planner
Paper Positioning Planner
Decide what the paper is selling, to whom, against which closest work, and with what evidence.
Use this skill when:
- a project has enough idea/literature/evidence to ask what the paper should be
- results are mixed and the contribution type may need to change
- a draft feels unfocused or overclaims beyond evidence
- figure review or reviewer simulation suggests the paper story is wrong
- the user needs a primary claim, secondary claims, title/abstract direction, intro thesis, or related-work boundary
- the paper may be a method paper, theory-guided method, empirical analysis, benchmark, diagnostic paper, systems paper, or negative/limitation paper
- the user is deciding between target audiences or venues before polishing the text
Do not use this skill as a paragraph-level writing adapter. Use conference-writing-adapter after the positioning decision is clear.
Pair this skill with:
research-idea-validatorwhen the whole project may need pursue/revise/park/kill
More from a-green-hand-jack/ml-research-skills
project-init
Initialize an ML research project control root. Use for paper/code/slides repos, shared memory, GitHub Project alignment, agent guidance, worktree policy, and lifecycle handoffs.
39init-python-project
Initialize or enhance a Python/ML project. Use for new repos or forks needing production structure, uv environment setup, and research evidence docs.
37new-workspace
Create Git branches or worktrees for research code and paper versions. Use for experiments, baselines, rebuttal fixes, arXiv/camera-ready branches, and worktree memory.
36project-sync
Sync verified code-side experiment results into paper memory. Use when logs, reports, run docs, or user-confirmed metrics should become paper-facing evidence.
36init-latex-project
Initialize a LaTeX academic paper project. Use for new conference or journal papers needing templates, macros, venue preambles, and writing guidance.
36add-git-tag
Create annotated Git milestone tags. Use when completing a phase, releasing a version, or marking a research checkpoint.
36