findingslisted

# /findings — Populate docs/findings.md Draft, extend, refresh, or audit a project's `docs/findings.md`: the curated index of *what we have learned* that the project considers load-bearing for the paper or for downstream interpretation. Each entry is a confidence-tagged headline with an expanded explanation, anchored to build artifacts, reports, news, and cross-references through a standardized Sources footer. This skill is the *authoring* counterpart to `/findings-audit` (which audits findings against external evidence — different verb). Use `/findings` to write or maintain entries; use `/findings-audit` to stress-test the entries you've written. ## Arguments - `/findings` — infer project from cwd; default to populate-or-extend mode. - `/findings <project-slug>` — run against a specific project under `projects/`. - `/findings --extend` — preserve existing entries; only append new ones suggested by recent build artifacts, audit JSONs, or the user's pointer. - `/findings --refresh` — recompute the load-bearing numbers in entries against current build artifacts; flag entries whose headline numbers don't match the current data. Critical for catching staleness after pipeline reruns or parser fixes. - `/findings --audit` — do not write; report completeness gaps (missing source classes, missing confidence tags, dangling cross-refs, sources without page anchors). - `/findings --footer <slug-or-heading>` — re-format only the Sources footer of one specified entry to the standardiz