# Markdown To > Markdown To defines canonical, versioned Markdown specifications any agent can adopt — > `todo@0.1`, `kanban@0.1`, `audio@0.1`, `backlog@0.1` — where a conforming `.md` file is not > documentation about an application but its complete, portable state: readable in any viewer, > diffable in git, never captive to a tool. Canonical specs, open to every agent. The file owns > the state. Each linked document below is normative prose in the required five-part shape (Purpose, Grammar, Rationale, Examples, Verb reference) or, for conventions.md, the shared base every spec inherits. Read conventions.md first; a spec document defines only what is particular to it. ## Specifications - [Shared conventions](https://markdownto.ai/specs/conventions.md): the normative base every spec inherits — the frontmatter envelope, lazy `^id` identifiers, `[key:: value]` inline fields, `#tags`, `[[wikilinks]]`, preservation guarantees, and the shared `MDTO0xx` diagnostic codes. - [todo@0.1](https://markdownto.ai/specs/todo.md): a checklist or backlog as a plain Markdown file, and the shared item model `kanban@0.1` and `backlog@0.1` build on. - [kanban@0.1](https://markdownto.ai/specs/kanban.md): a board as a plain Markdown file — a level-2 heading is a column, a task item beneath it is a card. - [audio@0.1](https://markdownto.ai/specs/audio.md): a narration manuscript — headings are chapters, prose is the script, and sparse inline fields carry a narrator's direction. - [backlog@0.1](https://markdownto.ai/specs/backlog.md): a prioritized, dependency-aware backlog extending the todo item model with start/finish/block/promote/demote verbs. ## Code - [GitHub — seekinggradient/markdownto](https://github.com/seekinggradient/markdownto): every spec, schema, and conformance fixture, plus the CLI and renderer packages that implement them. Every document above is also what `mdto spec ` prints locally — `` is `conventions`, `todo`, `kanban`, `audio`, or `backlog` — so an agent that already has the CLI never needs to fetch these at all.