Docs Discipline

A page the reader skims and gets. Every fact is shown by the device that shows it fastest, and a paragraph carries only what no device shows. Every path, symbol, and check it names is real. A probe makes the two mechanical readings exact.

Repository documentation is read by a programmer in a hurry and by agents, and this skill owns its shape and its facts. PR bodies and issues belong to the /pr-and-issue-discipline skill, AGENTS.md to the /code-standards skill.

Where /unslop is installed, it runs last over the prose that remains.

The specimen

One paragraph of a fleet guide (all-green.md at 7cb9aa3f), 71 words carrying three rules and two exceptions:

The judgment, whole: every needed result must be `success`, or `skipped` for a job named in `allowed-skips`. Anything else (`failure`, `cancelled`, a skip the list does not name) fails the gate, and the step summary lists every job with its result. The managed skeleton names `checks` alone, so a schedule night passes on `ci` and an all-skipped run cannot pass; repo-platform's own ci.yml names nothing, since none of its gating jobs may skip.

The same facts, shown: