From tasks-board
This skill should be used when the user asks about "tasks board", "task management", "epic management", "subtask tracking", "kanban board", or wants to create, update, organize, or view tasks stored as markdown files in epic directories. Also trigger when the user says "show my tasks", "open the board", or "manage tasks".
npx claudepluginhub m86-ai/claude-marketplace --plugin tasks-boardThis skill uses the workspace's default tool permissions.
Visual task management backed by a directory of markdown files. Each epic is a subdirectory, each task is a `.md` file, and subtasks are checkbox items within the file.
Defines conventions for TASKS.md files: structure with optional sections, status symbols ([ ] todo, [/] ongoing, [x] done, [-] backlog), task descriptions, and testable acceptance criteria. Use for creating, editing, updating tasks or tracking progress.
Manages tasks in TASKS.md with Active/Waiting/Someday/Done sections; add/complete/summarize tasks, extract from conversations, setup HTML dashboard.
Organizes markdown task files into folders like tasks/, ideas/, templates/, bugs/ with YAML frontmatter defining types (task, idea, bug), due dates, tags, status. Use when creating or modifying task files.
Share bugs, ideas, or general feedback.
Visual task management backed by a directory of markdown files. Each epic is a subdirectory, each task is a .md file, and subtasks are checkbox items within the file.
tasks/
├── epic-name/
│ ├── _description.md # Epic metadata (optional)
│ ├── task-slug.md # Individual task
│ └── another-task.md
└── another-epic/
└── ...
# Task Title
Optional description text here.
**Priority:** high | medium | low
**Status:** todo | in-progress | done | blocked
**Created:** 2026-01-15
**Owner:** name
- [x] Completed subtask
- [ ] Pending subtask
# Epic Display Name
Optional description of the epic's scope.
Zero-dependency Node.js server using only built-in modules (http, fs, path). Vanilla HTML/CSS/JS client — no React, no build step.
| Method | Path | Purpose |
|---|---|---|
| GET | /api/epics | List all epic directories |
| GET | /api/tasks | List all tasks (sorted by prefs) |
| GET | /api/tasks/:epic/:slug | Get single task |
| PUT | /api/tasks/:epic/:slug | Update task (merge with existing) |
| POST | /api/tasks | Create new task |
| DELETE | /api/tasks/:epic/:slug | Delete task file |
| GET | /api/prefs | Get user preferences |
| PATCH | /api/prefs | Update preferences |
| Var | Default | Purpose |
|---|---|---|
| PORT | 3456 | Server port |
| TASKS_DIR | ../../tasks relative to server.js | Path to tasks directory |
| PREFS_FILE | ./prefs.json relative to server.js | User preferences file |
.md files immediatelyCreate a new .md file in the appropriate epic directory following the task file format above. The server picks it up on next API call.
Create a new subdirectory under the tasks directory. Optionally add _description.md with a # Name heading.
For bulk status changes, use the API directly:
curl -X PUT http://localhost:3456/api/tasks/epic-id/task-slug \
-H 'Content-Type: application/json' \
-d '{"status": "done"}'
references/api-contract.md — Full API request/response examplesreferences/file-format.md — Detailed markdown parsing rules