docslisted

# docs Renders as a docsify site by default — plain markdown that also reads correctly on GitHub. ## Invocation `/wss:docs` invokes this skill by name, and `--wss-docs` fires it through the hook — both are the same request. (`--wss-diagram` also lands here: a single inline diagram routed into the site's annex, with the whole procedure carried by that flag's hook block rather than by a section of this file.) Bare, either means *document what we just worked on*: infer the target from the conversation — the files touched this session, the feature just built — and say what you picked before writing. With an argument (`--wss-docs auth`, `--wss-docs the map module`) that's the target. **`--wss-adopt` also invokes this** when it finds a project with no documentation at all, wanting Scaffold mode and the overview page — not a full site. It confers its own grant, which is commit and not push, so what gets scaffolded there may be committed even though this flag alone authorizes nothing. **`--wss-catalog` does not come through here once the page exists.** A changed `WSS.record.tooling.catalog` is a mechanical re-derivation, so it goes straight to `docs-writer` with the catalog as the source — the interaction diagram included, which that procedure re-renders for this site's renderer rather than reshaping by hand. This skill is reached only when the **Claude tooling** annex page does not exist yet, because that is a placement decision (T11) and placement is what this skill is for. #