Update to TaskPlanner

Snapshot Nov 9, 2026 · 12:07 UTC · version 3.0.18

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for taskplanner

Skill instructions — Now says: --- name: taskplanner description: Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints,...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save TaskPlanner and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 23:13 UTC

--- 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 Task...

After

Nov 9, 2026 · 12:07 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,64 +1,64 @@
----
-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:2.1.1 -->
-
-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.
-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_data` when structured board data is useful and `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.
+---
+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.18 -->
+
+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.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: taskplanner\ndescription: 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.\n---\n\n# TaskPlanner\n\n\n\nTaskPlanner 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.\n\n## Version preflight\n\nRun this once before the first TaskPlanner operation in a Codex/Cursor task:\n\n1. Read `.tasks/config.json` and compare `taskplannerVersion` with the embedded version above. Strip SemVer build metadata such as `+codex.*` before comparing.\n2. If the stored value is missing, malformed, or older, follow the sibling `update-taskplanner` skill before continuing.\n3. If equal, continue without writes.\n4. If the stored value is newer, warn that the installed plugin is older and do not downgrade managed files.\n\nThe installed skill bundle is authoritative. Never query GitHub or invoke a marketplace update.\n\n## Board files\n\nUse 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.\n\nEach task is a complete section from its `## ID: Title` heading through its trailing `---` separator:\n\n```markdown\n## TASK-001: Task title\n**Priority:** P1 | **Tags:** tag1, tag2\n\nDescription.\n\n### Plan\n\n- Step 1\n\n---\n```\n\n## MCP path\n\nPrefer `taskplanner_board`, `taskplanner_list`, `taskplanner_get`, `taskplanner_create`, `taskplanner_move`, and `taskplanner_update`. Use `taskplanner_board_data` when structured board data is useful and `taskplanner_board_visual` only when the host renders MCP Apps.\n\n## Direct file path\n\n- List by reading configured state files and parsing `##` sections.\n- 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.\n- Update only the selected task section; preserve its ID and every unrelated section.\n- Move by cutting the complete section, including its separator, from the source state file and inserting it into the target state file.\n- Preserve user configuration choices and all content outside the selected task or TaskPlanner marker blocks.\n\n## Implementing work\n\n1. Select the highest-priority task from Next, then Backlog, unless the user chose one.\n2. Move it to In Progress before substantive implementation.\n3. When `aiPlanRequired` is true, add a concise `### Plan` before coding.\n4. Implement and verify the work.\n5. Condense the plan to a done-summary and move the task to Done.\n6. Add one short entry at the top of `.tasks/WORK_LOG.md` when it exists.\n7. Add a `CHANGELOG.md` entry under `## [Unreleased]` when repository guidance requires it.\n\nNever change task IDs or modify unrelated task sections.\n"

AFTER

"---\r\nname: taskplanner\r\ndescription: 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.\r\n---\r\n\r\n# TaskPlanner\r\n\r\n\r\n\r\nTaskPlanner 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.\r\n\r\n## Version preflight\r\n\r\nRun this once before the first TaskPlanner operation in a Codex/Cursor task:\r\n\r\n1. Read `.tasks/config.json` and compare `taskplannerVersion` with the embedded version above. Strip SemVer build metadata such as `+codex.*` before comparing.\r\n2. If the stored value is missing, malformed, or older, follow the sibling `update-taskplanner` skill before continuing.\r\n3. 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.\r\n4. If the stored value is newer, warn that the installed plugin is older and do not downgrade managed files.\r\n\r\nThe installed skill bundle is authoritative. Never query GitHub or invoke a marketplace update.\r\n\r\n## Board files\r\n\r\nUse 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.\r\n\r\nEach task is a complete section from its `## ID: Title` heading through its trailing `---` separator:\r\n\r\n```markdown\r\n## TASK-001: Task title\r\n**Priority:** P1 | **Tags:** tag1, tag2\r\n\r\nDescription.\r\n\r\n### Plan\r\n\r\n- Step 1\r\n\r\n---\r\n```\r\n\r\n## MCP path\r\n\r\nPrefer `taskplanner_board`, `taskplanner_list`, `taskplanner_get`, `taskplanner_create`, `taskplanner_move`, and `taskplanner_update`. Use `taskplanner_board_visual` only when the host renders MCP Apps.\r\n\r\n## Direct file path\r\n\r\n- List by reading configured state files and parsing `##` sections.\r\n- 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.\r\n- Update only the selected task section; preserve its ID and every unrelated section.\r\n- Move by cutting the complete section, including its separator, from the source state file and inserting it into the target state file.\r\n- Preserve user configuration choices and all content outside the selected task or TaskPlanner marker blocks.\r\n\r\n## Implementing work\r\n\r\n1. Select the highest-priority task from Next, then Backlog, unless the user chose one.\r\n2. Move it to In Progress before substantive implementation.\r\n3. When `aiPlanRequired` is true, add a concise `### Plan` before coding.\r\n4. Implement and verify the work.\r\n5. Condense the plan to a done-summary and move the task to Done.\r\n6. Add one short entry at the top of `.tasks/WORK_LOG.md` when it exists.\r\n7. Add a `CHANGELOG.md` entry under `## [Unreleased]` when repository guidance requires it.\r\n\r\nNever change task IDs or modify unrelated task sections.\r\n"

Full snapshot data

{
"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.",
"included_files": [],
"name": "taskplanner",
"skill_md_contents": "---\r\nname: taskplanner\r\ndescription: 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.\r\n---\r\n\r\n# TaskPlanner\r\n\r\n\r\n\r\nTaskPlanner 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.\r\n\r\n## Version preflight\r\n\r\nRun this once before the first TaskPlanner operation in a Codex/Cursor task:\r\n\r\n1. Read `.tasks/config.json` and compare `taskplannerVersion` with the embedded version above. Strip SemVer build metadata such as `+codex.*` before comparing.\r\n2. If the stored value is missing, malformed, or older, follow the sibling `update-taskplanner` skill before continuing.\r\n3. 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.\r\n4. If the stored value is newer, warn that the installed plugin is older and do not downgrade managed files.\r\n\r\nThe installed skill bundle is authoritative. Never query GitHub or invoke a marketplace update.\r\n\r\n## Board files\r\n\r\nUse 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.\r\n\r\nEach task is a complete section from its `## ID: Title` heading through its trailing `---` separator:\r\n\r\n```markdown\r\n## TASK-001: Task title\r\n**Priority:** P1 | **Tags:** tag1, tag2\r\n\r\nDescription.\r\n\r\n### Plan\r\n\r\n- Step 1\r\n\r\n---\r\n```\r\n\r\n## MCP path\r\n\r\nPrefer `taskplanner_board`, `taskplanner_list`, `taskplanner_get`, `taskplanner_create`, `taskplanner_move`, and `taskplanner_update`. Use `taskplanner_board_visual` only when the host renders MCP Apps.\r\n\r\n## Direct file path\r\n\r\n- List by reading configured state files and parsing `##` sections.\r\n- 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.\r\n- Update only the selected task section; preserve its ID and every unrelated section.\r\n- Move by cutting the complete section, including its separator, from the source state file and inserting it into the target state file.\r\n- Preserve user configuration choices and all content outside the selected task or TaskPlanner marker blocks.\r\n\r\n## Implementing work\r\n\r\n1. Select the highest-priority task from Next, then Backlog, unless the user chose one.\r\n2. Move it to In Progress before substantive implementation.\r\n3. When `aiPlanRequired` is true, add a concise `### Plan` before coding.\r\n4. Implement and verify the work.\r\n5. Condense the plan to a done-summary and move the task to Done.\r\n6. Add one short entry at the top of `.tasks/WORK_LOG.md` when it exists.\r\n7. Add a `CHANGELOG.md` entry under `## [Unreleased]` when repository guidance requires it.\r\n\r\nNever change task IDs or modify unrelated task sections.\r\n"
}

SHA-256 of public snapshot: 77acfb6f375f998306c81527ea6d9372f3dbda1814e0ec3b1ff2dfb6c25ed0e5