Documents

Documents are where specs, runbooks, and decisions live: in the same repository as the code they describe, one keystroke from the issues and PRs they explain (G D).

Create and edit

Documents use a block editor with slash commands: type / for headings, lists, code blocks, and the rest. Editing is real-time collaborative; everyone in the doc sees everyone else's cursor and edits merge live, with no save button and no lock.

The same editor and the same collaboration engine power issue and PR bodies, so there is exactly one writing experience across the product.

Markdown in and out

Documents import from and export to markdown. Bring an existing docs/ folder over, or pull a doc out as .md when something needs to leave the platform:

pln doc list --repo <org>/my-app
pln doc create --repo <org>/my-app --title "Release runbook" --body-file ./runbook.md

Linking docs to work

Docs participate in relations: relate a spec to the issues implementing it, attach a doc to a chat message as a rich card, and find it again from either end. A doc is a node in the same graph as everything else, not a file in a second product.

Generated and read-only docs

Some docs are produced rather than written: a GitHub import converts wiki pages, and agents can create and maintain docs. Generated docs can be marked read-only so the source of truth stays wherever generates them.