docslisted
Install: claude install-skill backchainai/backchain-plugins
# Docs
Route one document to the mode it belongs in, write it under that mode's constraints, then check its markdown form.
The unit of work is one document and one next action. This skill does not plan a documentation set top-down, does not audit a whole `docs/` tree in one pass, and does not produce an outline for a future set of pages.
Two paths share the same routing step: writing a new document (the write path) and assessing one that already exists (the place path). Both start at the compass below, and both end at the same markdown-form check.
## Where this does not apply
Diataxis governs product documentation written for a user. It does not govern everything that happens to be a markdown file in a repository.
Check the request against this table before routing anything:
| Out of scope | Why |
|---|---|
| ADRs and decision records | A dated historical artifact, not one of the four modes |
| Commit messages, PR descriptions | Not user documentation |
| Changelogs, release notes | Chronological by nature; no mode applies |
| Code comments and docstrings | Belong to the code, not the documentation set |
| `CLAUDE.md`, agent and tool config | Instructions to a machine, not a user |
| READMEs | A landing page, legitimately hybrid; advise, do not split |
When the request names one of these, say which row applies and stop before opening the compass.
None of the four modes fits an artifact that is fundamentally dated, historical, or machine-facing.
The README row is a d