plan-submission
/plan-submission
Buduje wsteczny harmonogram zgłoszenia na konferencję od terminu: dni do końca (AoE), rejestracja abstraktu, zamrożenie autorów, konta w systemach, limity materiałów i audyt podwójnego zgłoszenia.
- Autor
- ShaishavMaisuria ↗
- Repozytorium
- research-paper-lifecycle-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 3
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 3 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/build_timeline.py, scripts/fetch_page.py, scripts/venue_profile.py
Co robi i kiedy
Buduje wsteczny harmonogram zgłoszenia na konferencję od terminu: dni do końca (AoE), rejestracja abstraktu, zamrożenie autorów, konta w systemach, limity materiałów i audyt podwójnego zgłoszenia.
Wyzwalacze z opisu
Oryginalny opis (EN)
Builds a backwards submission timeline from a conference deadline - days remaining (AoE-aware), abstract-registration offsets, author-list freeze, OpenReview/CMT/EasyChair/HotCRP/PCS account lead times and per-system steps, supplementary-material and code size limits, reciprocal-reviewing duties, and a dual-submission audit. Use when the user wants to plan a submission, asks how long until a deadline, mentions abstract registration, submission checklist, deadline countdown, "what do I need before the NeurIPS/ICML/CHI deadline", or asks what happens after submitting (rebuttal window, notificati
Jak działa
- When to use
- Inputs
- Process
- Output
- Guardrails
- Bundled files
Podgląd SKILL.md
---
name: plan-submission
description: Builds a backwards submission timeline from a conference deadline - days remaining (AoE-aware), abstract-registration offsets, author-list freeze, OpenReview/CMT/EasyChair/HotCRP/PCS account lead times and per-system steps, supplementary-material and code size limits, reciprocal-reviewing duties, and a dual-submission audit. Use when the user wants to plan a submission, asks how long until a deadline, mentions abstract registration, submission checklist, deadline countdown, "what do I need before the NeurIPS/ICML/CHI deadline", or asks what happens after submitting (rebuttal window, notification, camera-ready). Phase-aware - produces pre-submission, under-review, and camera-ready plans from venues/ profiles and flags overdue steps.
---
# Plan Submission
Turn "the deadline is in N weeks" into a dated, phase-aware milestone plan.
Works backwards from the paper deadline (or forwards through rebuttal and
camera-ready if the deadline already passed), anchored to a
`venues/conferences/<venue>-<year>.yml` profile. Companion skills:
`parse-cfp` (creates the profile), `preflight-check` (the T-3d desk-reject
lint), `write-rebuttal`, `prepare-camera-ready`.
## When to use
- "Plan my SIGSPATIAL submission" / "what do I need to do before the deadline?"
- "How many days until the NeurIPS deadline?" (AoE confusion included)
- "When do I have to register the abstract?" / "when does the rebuttal start?"
- The user just picked a venue (via `select-venue`) and asks "what now?"
## Inputs
- A venue + year (and ideally a track). The profile must exist at
`venues/conferences/<venue>-<year>.yml`; if it does not, run `parse-cfp`
first — never plan from remembered dates.
- Today's date, and any user-specific constraints (vacations, co-author
availability, experiments still running).
- `CONTACT_EMAIL` env var if the live re-verification fetch is used.
## Process
1. **Resolve the venue profile.** Locate
`venues/conferences/<venue>-<year>.yml`. Missing or from a previous
cycle → route through `parse-cfp` to create/refresh it before planning.
Check the profile's `verified:` block — if `confidence` is not
`verified-live` or `verified.date` is old, treat every date as suspect.
2. **Re-verify the critical dates against the live CFP.** Mandatory before
the user relies on the plan. Run:
```
python3 scripts/fetch_page.py "<cfp_url from the profile>"
```
Confirm the abstract deadline, paper deadline, and timezone on the live
page (deadlines slip mid-cycle — extensions are common, but so are
silent corrections). On mismatch, update the profile first. If the page
is JS-rendered or down, say so and mark the plan "dates unverified".
3. **Build the timeline.** Run:
```
python3 scripts/build_timeline.py venues/conferences/<venue>-<year>.yml \
--track "<track>" --today YYYY-MM-DD
```
The script is offline and deterministic: it detects the current phase
(pre-submission / under-review / camera-ready), computes days remaining
for every profile deadline, and emits dated milestones with standard
backwards offsets (T-21d dual-submission audit and reciprocal-reviewing
check, T-14d system accounts, T-10d author-list freeze, abstract
registration at its real date, T-5d supplementary, T-3d preflight, T-2d
draft upload, T-1d final upload). `--camera-ready YYYY-MM-DD` supplies a
deadline the profile lists as null. `--format json` for machine use.
4. **Customize the milestones** using
[references/milestone-playbook.md](references/milestone-playbook.md):
what each milestone actually requires, why the offset is what it is,
supplementary/code size limits, reciprocal-reviewing mechanics, and the
AoE math. Adjust offsets for the user's constraints (e.g. co-author on
leave at T-10d → freeze the author list earlier). Never move a HARD
deadline; only prep milestones are adjustable.
5. **Add per-system steps** from
[references/submission-systems.md](references/submission-systems.md) for
the profile's `review.submission_system` — account lead times (OpenReview
profile moderation can take ~2 weeks), what the submission form demands,
conflict-of-interest entry, and each system's signature gotcha (HotCRP's
"ready for review" checkbox, PCS metadata lock, EasyChair co-author email
typos, CMT COI lists).
6. **Run the dual-submission audit interactively.** Quote the profile's
`review.dual_submission` policy verbatim, then ask the user to inventory
every overlapping manuscript by ANY co-author that is under review or
planned elsewhere (including workshop versions and arXiv plans). Flag
conflicts against the quoted policy; when the policy is ambiguous, say
so and point at the CFP — do not adjudicate.
7. **Present the plan**: phase, key-dates table with days remaining,
milestone table (OVERDUE items first, called out explicitly), per-system
steps, policy gates, and the re-verify warning. If the paper deadline
has already passed, do NOT pretend otherwise — plan the next phase and
say plainly which deadlines are gone.
## Output
A dated submission plan in Markdown: current phase, key dates with
days-remaining (timezone noted), backwards milestone schedule with status
(in Nd / TODAY / OVERDUE / PASSED), submission-system checklist, policy
gates (dual submission, LLM policy, reciprocal reviewing), and the closing
notice: *"Dates from `<profile>` (verified `<date>`). Re-verified against
`<cfp_url>` on `<today>`. Deadlines change mid-cycle — check the CFP again
before each milestone."*
## Guardrails
- Never invent a date. A `null` in the profile stays unknown in the plan,
with an instruction on where to find it — a guessed deadline is worse
than none.
- Always state the timezone next to every deadline. AoE is common, not
universal (SIGSPATIAL uses Pacific Time); a wrong assumption costs a day.
- Never submit, register, create accounts, or click anything in any
submission system on the user's behalf. The plan tells the user what to
do; the user does it.
- Past deadlines are reported as passed, never silently dropped or
rescheduled.
- One page per fetch-script invocation; cache stays under `.cache/`
(gitignored); never commit fetched CFP text.
## Bundled files
- [references/milestone-playbook.md](references/milestone-playbook.md) —
what every milestone requires, default offsets and their rationale,
supplementary/code limits, reciprocal reviewing, dual-submission audit,
AoE math.
- [references/submission-systems.md](references/submission-systems.md) —
per-system walkthroughs: OpenReview, CMT, EasyChair, HotCRP, PCS.
- `scripts/build_timeline.py` — deterministic phase-aware timeline builder
(run it; do not compute date arithmetic by hand).
- `scripts/fetch_page.py` — polite single-page fetcher for live CFP
re-verification (vendored from `parse-cfp` so this skill is
self-contained).
- `scripts/venue_profile.py` — shared profile loader (YAML-subset parser +
family merge), vendored for self-containment.
Pliki w paczce (6)
- SKILL.md 7 KB
- references/milestone-playbook.md 11 KB
- references/submission-systems.md 9 KB
- scripts/build_timeline.py 21 KB
- scripts/fetch_page.py 12 KB
- scripts/venue_profile.py 12 KB
Wersje
W bazie nie ma innych skilli o nazwie plan-submission.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 12927f13d9c5 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100parse-cfp
Parsuje stronę Call for Papers do karty wymagań (terminy ze strefami, limity stron, tryb recenzji, szablon LaTeX, polityka AI) w pliku YAML profilu konferencji. - 100write-abstract
Pisze, przepisuje i sprawdza abstrakty artykułów pod wymogi konferencji (np. LNCS 150 do 250 słów), generuje blok słów kluczowych i przygotowuje pakiet rejestracji abstraktu. - 100submission-portal
Tworzy, czyta i zmienia zgłoszenie pracy w portalu HotCRP przez paperlint: tematy, konflikty, PDF i abstrakt oraz weryfikację sumą sha256. - 100conference-abstract-adaptor
Dostosowuje abstrakty naukowe do limitów słów, reguł sekcji i wymogów formatowania konkretnej konferencji, przy przekształcaniu istniejącego abstraktu do zgłoszenia. - 100rebuttal
Przetwarza recenzje naukowe i przygotowuje bezpieczną odpowiedź autorów w formie tekstowej, w limitach konferencji i kolejnych rundach. - 90conference-abstract-writer
Skraca pełne badanie do formatu abstraktu konferencyjnego: dopasowuje limity słów i znaków, strukturę Background/Methods/Results/Conclusion i wymagane nagłówki, na przykład ASCO lub AACR.