Individual skill

dac-related-work

Use when writing or auditing the related-work and positioning of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the EDA literature lanes (DAC/ICCAD/DATE/ASP-DAC/TCAD/TODAES), delta-first positioning against the strongest prior tool, honest benchmark-suite lineage, and third-person self-citation under double-blind review within the six-page budget.

DAC-Skills/skills/dac-related-work/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,403
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DAC Related Work

Position the paper against the EDA literature a DAC reviewer already knows. At six double-column
pages, related work is not a survey — it is a **delta statement**: here is the best prior technique
for this design task, here is precisely what it cannot do, here is what we add, measured in QoR.
DAC reviewers are drawn from exactly the subcommittee whose prior work you are extending, so an
incomplete or unfair positioning is caught immediately.

## The EDA literature lanes

Cover the lanes your contribution touches; do not pad with distant ones:

- **The top EDA venues** — DAC, **ICCAD**, **DATE**, **ASP-DAC** — the conference record of your
  problem. A physical-design paper that cites no recent DAC/ICCAD placement work reads as
Back to top