My coding agents don't need a project management tool. They need markdown files.

Description and use

Coding agents don't need a paid task tracker; they need Markdown files. With board.md they read and update status directly in the repo, avoiding API calls and plan limits.

Problem

Agents required a task tracker that was costly and limited; they only needed simple file-based tasks.

Outcome

Agents can now read and edit tasks directly in the repo, eliminating API costs and simplifying status updates; board.md provides a lightweight kanban view.

Workflow

• Create markdown task files with YAML frontmatter
• Run npx boardmd init to generate config
• Run npx boardmd serve --open to view board
• Drag card to change status, which updates one line in file
• Agents use boardmd commands to list, create, set, and check tasks

Evidence

An agent needs a file it can read and edit. One markdown file per task, in the repo, with the fields in YAML frontmatter and the notes below:

Source

board.md reads the files you have. npx boardmd init looks at them and works out a config: the id format, the statuses, which fields become badges or filters.

Source

When I drag a card, exactly one line of one file changes: -status: todo +status: in-progress

Source

boardmd list --json: Every open task with its fields, its file and its live state from git.

Source