taskplanner
/taskplanner
Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints, or asks to create, implement, update, list, or move TaskPlanner tasks. Prefer TaskPlanner MCP tools when they can access the active workspace and otherwise operate on the files directly.
- Author
- smekai ↗
- Repository
- taskplanner ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints, or asks to create, implement, update, list, or move TaskPlanner tasks. Prefer TaskPlanner MCP tools when they can access the active workspace and otherwise operate on the files directly.
Original author description
Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints, or asks to create, implement, update, list, or move TaskPlanner tasks. Prefer TaskPlanner MCP tools when they can access the active workspace and otherwise operate on the files directly.
How it works
- Version preflight
- Board files
- MCP path
- Direct file path
- Implementing work
SKILL.md preview
--- name: taskplanner description: Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints, or asks to create, implement, update, list, or move TaskPlanner tasks. Prefer TaskPlanner MCP tools when they can access the active workspace and otherwise operate on the files directly. --- # TaskPlanner <!-- TASKPLANNER:VERSION:3.0.22 --> TaskPlanner stores a git-tracked board in `.tasks/`. Use MCP tools when available, always passing the absolute active repository as `workspace_root`. If a tool is unavailable or cannot see that repository, use the direct file workflow below without blocking the user. ## Version preflight Run this once before the first TaskPlanner operation in a Codex/Cursor task: 1. Read `.tasks/config.json` and compare `taskplannerVersion` with the embedded version above. Strip SemVer build metadata such as `+codex.*` before comparing. 2. If the stored value is missing, malformed, or older, follow the sibling `update-taskplanner` skill before continuing. 3. If equal, continue without writes, except when the `upgradeChecks` array in the config is missing or lacks `"3.0"`: then run the sibling `update-taskplanner` skill's **Upgrading to 3.0** checks first. 4. If the stored value is newer, warn that the installed plugin is older and do not downgrade managed files. The installed skill bundle is authoritative. Never query GitHub or invoke a marketplace update. ## Board files Use the `states` mapping in `.tasks/config.json`; defaults are Backlog (`BACKLOG.md`), Next (`NEXT.md`), In Progress (`IN_PROGRESS.md`), Done (`DONE.md`), and Rejected (`REJECTED.md`). `WORK_LOG.md` is an optional completion log, not a state. Each task is a complete section from its `## ID: Title` heading through its trailing `---` separator: ```markdown ## TASK-001: Task title **Priority:** P1 | **Tags:** tag1, tag2 Description. ### Plan - Step 1 --- ``` ## MCP path Prefer `taskplanner_board`, `taskplanner_list`, `taskplanner_get`, `taskplanner_create`, `taskplanner_move`, and `taskplanner_update`. Use `taskplanner_board_visual` only when the host renders MCP Apps. ## Direct file path - List by reading configured state files and parsing `##` sections. - Create by reading `idPrefix` and `nextId`, generating the padded ID, incrementing and saving `nextId`, then inserting one complete section at the configured top/bottom position. - Update only the selected task section; preserve its ID and every unrelated section. - Move by cutting the complete section, including its separator, from the source state file and inserting it into the target state file. - Preserve user configuration choices and all content outside the selected task or TaskPlanner marker blocks. ## Implementing work 1. Select the highest-priority task from Next, then Backlog, unless the user chose one. 2. Move it to In Progress before substantive implementation. 3. When `aiPlanRequired` is true, add a concise `### Plan` before coding. 4. Implement and verify the work. 5. Condense the plan to a done-summary and move the task to Done. 6. Add one short entry at the top of `.tasks/WORK_LOG.md` when it exists. 7. Add a `CHANGELOG.md` entry under `## [Unreleased]` when repository guidance requires it. Never change task IDs or modify unrelated task sections.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · smekai/taskplanner | 100 | MIT |
| smekai/taskplanner | 100 | MIT |
Database snapshot: 13.11.2026 · package version f881c152f679 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100update-taskplanner
Synchronize an existing TaskPlanner project with the installed skill version. Use for update, upgrade, migrate, refresh, or sync requests and for the TaskPlanner version preflight; update only TaskPlanner-owned marker blocks and safe config defaults without changing tasks or user choices. - 100update-taskplanner
Synchronize an existing TaskPlanner project with the installed skill version. Use for update, upgrade, migrate, refresh, or sync requests and for the TaskPlanner version preflight; update only TaskPlanner-owned marker blocks and safe config defaults without changing tasks or user choices. - 100backlog
Manage this workspace's Markdown tasks through Backlog.md. Use when creating, splitting, selecting, tracking, or closing tasks, or when the user mentions the backlog, task IDs, acceptance criteria, or a Definition of Done. - 100kaneo
Operate Kaneo project tracking over its REST API or built-in HTTP MCP - list workspaces, projects, tasks, comments, labels, and columns; create or update tasks and related records. Use when the user says kaneo, Kaneo ticket, log this in Kaneo, or asks to create or update a Kaneo task. - 100myco
Manage project state via the myco CLI — tasks, backlog, issues, proposals, plans, ADRs, handoffs in `project/` worktree files. Trigger when working with `project/` files, planning, tracking tasks, or starting/resuming work. - 100flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).