ase-workflow
Use when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in both IEEE Xplore and the ACM Digital Library.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-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.
# ASE Workflow Run the ASE year backward from the deadline. ASE is an annual conference (dual IEEE/ACM sponsored) whose research track has an **early-rejection gate**, a **rebuttal**, and a first-class, criteria-bound **Revision** outcome; plan for all three. Every date below is a one-cycle snapshot — reopen the current Important Dates page first (see `resources/official-source-map.md`). ## Anchor dates (ASE 2026 snapshot — verify each cycle) - **Research submission:** 26 March 2026. **Notification:** 25 May 2026. **Conference:** Munich, Germany, 12-16 October 2026. - The **abstract-registration deadline** preceding the full-paper deadline is **待核实** — confirm it; it is a hard gate. - As of 2026-07-09 the ASE 2026 notification has passed. The next *submission* target is **ASE 2027** (host/dates **待核实**). Reverify before planning. ## Backward plan from the deadline ```text T-16 wk Route with ase-topic-selection: ASE research vs. NIER/Tools vs. FSE/ISSTA/journal. T-14 wk Lock the automation and the subject systems; freeze what the tool does and what it runs on. T-10 wk Build evidence (ase-experiments): real subjects, fair tool baselines, ablation isolating any learned component. Pin
- Anchor dates (ASE 2026 snapshot — verify each cycle)
- Backward plan from the deadline
- After submission — the review timeline
- Track fork (decide early, they have separate deadlines and sites)
- Risk register (ASE-specific)
- Parallelizable vs. sequential
- Output format
What does the ase-workflow skill do?
Use when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in both IEEE Xplore and the ACM Digital Library.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-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.