extend-paperlisted
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:436bb3586d84a654 compiled from skills/extend-paper/SKILL.md.spec.ts -->
# extend-paper — workshop/short paper → a second, stronger publication
## Run me
🔴 FIRST, before any other step:
```
node .claude/skills/paper-pipeline/scripts/announce.mjs extend-paper <paper-dir>
```
An advisory pass cannot be observed failing — silence is both its error state and its normal
state — so starting is an event, and events get written down.
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 submissi