<< All versions

Skill v1.0.1

currentAutomated scan100/100
zernie/paperlint/extend-paper

+7 new

──Details
PublishedOctober 13, 2026 at 10:26 AM
Content Hashsha256:1aad9c6064863c91...
Git SHA1092ca922c92
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 4.9 KB)
SKILL.md4.9 KBactive
SKILL.md · 70 lines · 4.9 KB

version: "1.0.1" name: extend-paper description: Turn an accepted workshop / short paper into a second, stronger publication at a higher-prestige indexed venue — the "body of work" a strong dossier needs, not a one-hit paper. Covers the ≥30% new-material rule, the never-dual-submit rule, what genuinely counts as new content, and picking + timelining the upgrade venue. Use after a paper is accepted and you want the follow-on publication. Compose with find-venue, plan-paper-timeline, camera-ready, research-ideate. allowed-tools: [Read, Write, Grep, Glob, WebSearch, WebFetch, Skill]


<!-- vigiles:sha256:6310b1e7748e10de compiled from skills/extend-paper/SKILL.md.spec.ts -->

extend-paper — workshop/short paper → a second, stronger publication

One accepted paper is a data point; two related papers climbing in prestige is a trajectory, and "sustained acclaim" is what a body-of-work review actually rewards. Workshop→conference and conference→journal extensions are a standard, expected move — venues invite them. The catch: an extension is new work that subsumes the old, not the same paper resubmitted. This skill is how to do it legitimately.

The two hard rules

  • ≥30% new material. Most venues (and ACM/IEEE self-plagiarism policy) require an extension to add

substantial new content — the common bar is roughly a third genuinely new. Not reformatting, not more words: new experiments, new analysis, new data. Cite the original workshop paper explicitly and state in the intro what's new ("this paper extends our workshop paper [X] with …").

  • Never dual-submit. One venue at a time, full stop. The workshop paper is done and indexed; the

extension goes to exactly one new venue and waits for its decision before going anywhere else. Simultaneous submission of the same/overlapping work is an ethics violation that can get both papers retracted — a dossier-killer.

What actually counts as new material

Pick the axis where the workshop paper was thin and build it out for real:

  • More coverage — more tools / venues / models / languages measured (a 3-tool study → 12 tools).
  • A deeper analysis axis — add a dimension the short paper only gestured at (cost and latency,

a failure taxonomy, an ablation over the method's knobs).

  • A field study or user study — take the lab measurement into a real deployment / real developers.
  • The residual-bug fix built out — the "future work" / limitation you named in Threats to Validity

becomes a full contribution (you designed the fix; now implement + evaluate it).

  • A stronger artifact — a benchmark others can run and cite, not just a repro of your own numbers.

If you can't honestly point to which ≥30% is new, it's not an extension yet — go back to research-ideate and find the new contribution first.

Pick the upgrade venue

Run find-venue — the target is a higher-prestige indexed home than the workshop, matched to the paper type:

  • A measurement / evaluation paper → MSR (Mining Software Repositories) or **NeurIPS

Datasets & Benchmarks** — venues that reward reusable measurement contributions.

  • A benchmark / security paper → a full security conference (the tier above the workshop it started

at), where the artifact is the headline.

  • Prefer venues that explicitly invite journal/conference extensions (many workshops, AgenticDev

included, say so in their CFP) — the extension path is sanctioned there. Verify the target's CFP the same way find-venue does: fetch it, confirm it accepts extensions of prior short papers, and check its self-plagiarism / overlap policy.

Timeline it (and space it out)

Run plan-paper-timeline against the upgrade venue's deadline, then deliberately space the submissions. A burst of papers clustered right before an external filing deadline reads as manufactured, not sustained — a documented reason for refusal, not a stylistic worry. Aim the extension to land a few months after the first paper's acceptance so the record shows steady output over time, one ORCID tying every version together.

Compose with

  • find-venue — choose the higher-prestige indexed target and confirm it welcomes extensions.
  • plan-paper-timeline — schedule the new experiments + write-up against the target deadline.
  • research-ideate — if the ≥30% new contribution isn't obvious yet, find it here first.
  • camera-ready — the accepted, de-anonymized, DOI'd base version you're extending from.

Provenance

The AgenticDev 2026 "Measuring the Wrong Number" workshop paper's planned extension to MSR 2027 (deadline ~Oct 23, 2026) or NeurIPS 2027 Evaluations & Datasets (~May 2027) — a second, stronger, higher-prestige indexed publication that turns one accepted paper into a body of work. AgenticDev's CFP explicitly invites journal extensions; the same ORCID links the workshop paper and its extension.

← v1.0.0All versions