paper-to-codelisted

# Paper-to-code: implementation without invention BLUF: the paper is the only source of truth; every implementation decision is either anchored to it or explicitly flagged as our choice. The dominant failure mode is silent gap-filling — plausible defaults presented as the paper's content. That is neuroslop in code form, and this skill exists to make it structurally impossible. ## Stage 0 — acquire the full text - Prefer arxiv-mcp tools (`download_paper` / `read_paper`) when available; otherwise WebFetch the abstract page and PDF. - Appendices, footnotes, table captions, and figure captions are first-class sources — missing hyperparameters usually live there, not in the method section. - If the authors published official code, locate it; it is a second, separately-tagged source — never a silent one. ## Stage 1 — ambiguity audit, before any code Classify every implementation-relevant decision; the tags below are this skill's specialization of the harness claim-typing discipline (epistemic boundary: confirmed ≠ associative): | Tag | Meaning | Obligation | |---|---|---| | `FACT §X.Y` / `Eq. N` | stated in the paper | anchor to the exact section/equation | | `PARTIAL §X.Y` | mentioned but ambiguous | quote the passage verbatim, list the readings | | `UNSPECIFIED` | paper is silent | our default + alternatives, never filled silently | | `ASSUMPTION` | inference from context | reasoning stated next to it | | `FROM-CODE` | taken from the authors' implementation | tagged as code