---
name: markdownto-kanban
description: Create or edit Markdown To boards whose columns express a clear workflow.
---
# Markdown To kanban
## Contract and workflow
Read `mdto spec kanban` (or the adjacent `SPEC.md` in a checkout) and the
[shared conventions](https://markdownto.ai/specs/conventions.md) before authoring or
repairing content. Outside a checkout, use the [published spec](https://markdownto.ai/specs/kanban.md).
This skill accompanies `[email protected]`. The spec and its fixtures govern conformance;
editorial advice below is non-normative and should adapt to the user's brief.
If the source declares another version, obtain its matching contract before changing it.
Use `markdownto: [email protected]`. Level-2 headings are columns, and cards are task items.
Read the done-column rules before choosing or moving columns: the rightmost column is
normally done, and crossing the done-role boundary changes the checkbox. Consult §5 for
card and column operations; do not assume todo's `move` semantics apply.
## Content quality
Name columns for meaningful workflow states and cards for outcomes. A person should be
able to tell what lets a card enter and leave a column. Prefer a few useful transitions to
a column for every activity. Keep explanatory detail with its card, and avoid duplicating
one deliverable across columns. Discuss overloaded active work as planning advice; do not
invent WIP enforcement or silently move the user's cards.
## Check and deliver
Validate the file with `mdto validate <path>` before editing existing content and again
after changes. Read diagnostics against the spec's rationale; preserve meaning when
repairing syntax. Prefer spec-owned verbs for edits they support, checking their current
`--help`; otherwise make a focused source edit, preserving unrelated content and IDs.
Render with `mdto render <path>` and inspect the result when available. Validation checks
structure, not editorial quality: review the content against the user's purpose as well.
Without the CLI, use the contract and examples and report that validation was not run.
Deliver the Markdown source and any requested artifacts, stating what was actually checked.
Give this guide to your agent, or read it as an author. It covers workflow and editorial judgment; the specification defines conformance.
Contract and workflow
Read mdto spec kanban (or the adjacent SPEC.md in a checkout) and the shared conventions before authoring or repairing content. Outside a checkout, use the published spec. This skill accompanies [email protected]. The spec and its fixtures govern conformance; editorial advice below is non-normative and should adapt to the user's brief. If the source declares another version, obtain its matching contract before changing it.
Use markdownto: [email protected]. Level-2 headings are columns, and cards are task items. Read the done-column rules before choosing or moving columns: the rightmost column is normally done, and crossing the done-role boundary changes the checkbox. Consult §5 for card and column operations; do not assume todo's move semantics apply.
Content quality
Name columns for meaningful workflow states and cards for outcomes. A person should be able to tell what lets a card enter and leave a column. Prefer a few useful transitions to a column for every activity. Keep explanatory detail with its card, and avoid duplicating one deliverable across columns. Discuss overloaded active work as planning advice; do not invent WIP enforcement or silently move the user's cards.
Check and deliver
Validate the file with mdto validate <path> before editing existing content and again after changes. Read diagnostics against the spec's rationale; preserve meaning when repairing syntax. Prefer spec-owned verbs for edits they support, checking their current --help; otherwise make a focused source edit, preserving unrelated content and IDs. Render with mdto render <path> and inspect the result when available. Validation checks structure, not editorial quality: review the content against the user's purpose as well. Without the CLI, use the contract and examples and report that validation was not run. Deliver the Markdown source and any requested artifacts, stating what was actually checked.