issta-workflow
Use when planning an ISSTA project timeline from venue fit through the January research-paper deadline, the March author response, the April first decision, the May Major-Revision sprint, the June final decision, artifact evaluation, and the October symposium, with backward-planning offsets for a testing/analysis tool paper and its artifact.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ISSTA Workflow Use this as the project-management skill for an ISSTA submission. Replace every date below with the current official timetable and work backward from the HotCRP deadline — ISSTA's calendar, and even its number of deadlines, changes between editions. ISSTA is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chair and Program Chairs, appointed by ACM SIGSOFT and turning over each year, and the cost model is registration, not APCs — proceedings appear in the ACM Digital Library. Re-check the current organization page rather than carrying a name forward. ## Milestones (2026 shape — verify the current cycle) - **Venue fit:** confirm the contribution is genuinely testing-and-analysis, not a broader SE result. - **Evidence lock:** freeze the technique's scope, the subjects and benchmark versions, the baselines, and the artifact plan. - **Submission deadline (Jan 29, 2026):** HotCRP record complete, 18-page anonymous `sigconf` PDF uploaded, subjects pinned. - **Author response (Mar 24-26, 2026):** rebuttal anchored in submitted evidence. - **First decision (Apr 16, 2026):**
- Milestones (2026 shape — verify the current cycle)
- Backward plan from the paper deadline
- Failure modes by stage
- Coordination notes
- Output format
What does the issta-workflow skill do?
Use when planning an ISSTA project timeline from venue fit through the January research-paper deadline, the March author response, the April first decision, the May Major-Revision sprint, the June final decision, artifact evaluation, and the October symposium, with backward-planning offsets for a testing/analysis tool paper and its artifact.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.