Task management agent. Auto-invoked for task creation, status tracking, and kanban board operations using Markdown files across lane directories. V2 enforces Kanban Sovereignty constraints preventing manual task file edits.
From task-managernpx claudepluginhub richfrem/agent-plugins-skills --plugin task-managerThis skill uses the workspace's default tool permissions.
acceptance-criteria.mdassets/templates/task-template.mdevals/evals.jsonevals/results.tsvfallback-tree.mdreferences/acceptance-criteria.mdreferences/fallback-tree.mdreferences/task-manager-workflow.mmdrequirements.txtscripts/next_number.pyscripts/task_manager.pyProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Transforms raw data into narratives with story structures, visuals, and frameworks for executive presentations, analytics reports, and stakeholder communications.
This skill requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txt
See ./requirements.txt for the dependency lockfile (currently empty — standard library only).
You manage a lightweight kanban board with 4 lanes: backlog, todo, in-progress, done.
Tasks are represented as standalone Markdown files (NNNN-title.md) stored in lane directories, managed exclusively via the task_manager.py CLI.
Canonical path (use this — agents run from the root of the current skill folder):
scripts/task_manager.py
This is the installed copy of the script. Always invoke with an absolute or root-relative path:
python3 ./scripts/task_manager.py <command>
Do NOT use ./task_manager.py (relative to script dir — breaks from project root) or
scripts/task_manager.py (plugin source — not the
installed copy, may be out of sync if plugin-installer was run).
The kanban board is a strictly managed directory state. Task IDs must be globally unique and sequentially numbered. The python CLI enforces all of this automatically.
NEVER create, rename, move, or delete task Markdown files using raw native tools (write_to_file, mv, cp, rm). Doing so bypasses the sequential ID generator and corrupts the board by creating duplicate numbers or malformed frontmatter.
ALWAYS use task_manager.py as the exclusive interface for all kanban operations. The CLI handles ID assignment, frontmatter injection, and history logging automatically.
NEVER report the current task state from memory. Boards change between tool calls.
ALWAYS run task_manager.py board after any state-change operation to show the user the live, current kanban state.
When executing task_manager.py:
1 stating a task ID does not exist, do not attempt to manually look for the file in the lane directories. Report the ID as not found and ask the user to confirm.references/fallback-tree.md.Always create the task with a short, descriptive title first to avoid filename length errors.
python3 ./scripts/task_manager.py create "Short Title" --lane todo
After creation, update the generated Markdown file to add full details, objectives, and acceptance criteria.
This two-step process ensures filenames remain valid and all task details are captured without error.
python3 ./scripts/task_manager.py board
python3 ./scripts/task_manager.py move 3 in-progress --note "Starting work"
python3 ./scripts/task_manager.py search "login"
Tasks are Markdown files stored in lane subdirectories (read-only for the agent, managed exclusively by the CLI):
tasks/backlog/tasks/todo/tasks/in-progress/tasks/done/