theorylisted

# /theory — Populate docs/theory.md Draft or extend a project's `docs/theory.md`: a structured inventory of formal theoretical frameworks that generate testable predictions the project's empirical design can adjudicate. ## Arguments - `/theory` — infer project from the current working directory. - `/theory <project-slug>` — run against a specific project under `projects/`. - `/theory --audit` — do not write; report coverage, dangling refs, and missing sections. - `/theory --extend` — preserve existing entries; only append new frameworks suggested by current evidence/literature. - `/theory --update <framework-id> [--artifact <AN-id-or-build-path>]` — **surgical single-framework edit**. Update one framework entry (prediction, scope, references) when a new analysis result or literature touchpoint changes how it applies to the project. Reads only `CLAUDE.md`, `theory.md`, and the optional triggering artifact. `--artifact` accepts either an AN id (preferred — e.g. `AN-019`; the skill reads `docs/analyses/an-019-*.md` to recover the relevant empirical content) or a raw `build/<path>` fallback. The framework entry's references back to evidence cite the AN id, not the build path. Does not re-derive other frameworks, does not re-walk `literature.md`/`hypotheses.md`. Use from `/next` step 5 when a run refines a single framework's empirical content. The `<framework-id>` argument is the entry number or name as used in `theory.md`. Numbering is sacred — never renumber (paper and hypoth