repo-task-board

You can manage Markdown tasks by storing them as plain-Markdown files under docs/tasks/issues/ with a standardized YAML frontmatter schema. This enables consistent lifecycle tracking, backlog grooming, and auto-generated board generation for repository work.

Repository task tracking uses plain-Markdown files with YAML frontmatter. Required fields include title, type, status, area, priority, owner, parent, blocks, blocked_by, created, and updated to ensure consistent parsing and governance.

Create a Markdown file under docs/tasks/issues/ with an appropriate slug and fill in the defined frontmatter fields. Then, regenerate docs/tasks/board.md to automatically produce an aggregated Kanban-style board view.

Markdown-based backlog grooming supports backlog, todo, doing, review, blocked, done, and drop states. These lifecycle statuses enable collaboration-friendly workflows and structured progress triage for repository epics.

Yes, plain-Markdown task boards support agent-ready planning and ROADMAP.md updates. The structured spec body and frontmatter schema enable consistent parsing for automated triage, epic tracking, and dependency management.

Using Markdown files for repository task management lacks a built-in backend database, relying entirely on file system parsing. Without strict adherence to the frontmatter schema, the auto-generated board.md and dependency tracking will fail to parse correctly.