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 continue-task

Skill instructions — Now says: --- name: continue-task description: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect...

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: continue-task description: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work. --- # Continue an In-Progress TaskPlanner Task 1. Run t...

After

Nov 9, 2026 · 12:07 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,16 +1,16 @@
----
-name: continue-task
-description: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.
----
-
-# Continue an In-Progress TaskPlanner Task
-
-1. Run the sibling `taskplanner` skill's version preflight once.
-2. Prefer `taskplanner_list` for In Progress and `taskplanner_get` for details, passing the absolute repository as `workspace_root`.
-3. If MCP cannot access the repository, read the In Progress file from the state mapping in `.tasks/config.json` and parse complete task sections directly.
-4. If none exist, suggest `next-task`; if several exist, ask which to resume.
-5. Follow the selected task's existing plan. Add a required missing plan before coding.
-6. Implement and verify the remaining work.
-7. Condense the plan, move the task to Done, add a top `.tasks/WORK_LOG.md` entry when present, and update `CHANGELOG.md` when required.
-
-Never change task IDs or modify unrelated task sections.
+---
+name: continue-task
+description: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.
+---
+
+# Continue an In-Progress TaskPlanner Task
+
+1. Run the sibling `taskplanner` skill's version preflight once.
+2. Prefer `taskplanner_list` for In Progress and `taskplanner_get` for details, passing the absolute repository as `workspace_root`.
+3. If MCP cannot access the repository, read the In Progress file from the state mapping in `.tasks/config.json` and parse complete task sections directly.
+4. If none exist, suggest `next-task`; if several exist, ask which to resume.
+5. Follow the selected task's existing plan. Add a required missing plan before coding.
+6. Implement and verify the remaining work.
+7. Condense the plan, move the task to Done, add a top `.tasks/WORK_LOG.md` entry when present, and update `CHANGELOG.md` when required.
+
+Never change task IDs or modify unrelated task sections.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: continue-task\ndescription: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.\n---\n\n# Continue an In-Progress TaskPlanner Task\n\n1. Run the sibling `taskplanner` skill's version preflight once.\n2. Prefer `taskplanner_list` for In Progress and `taskplanner_get` for details, passing the absolute repository as `workspace_root`.\n3. If MCP cannot access the repository, read the In Progress file from the state mapping in `.tasks/config.json` and parse complete task sections directly.\n4. If none exist, suggest `next-task`; if several exist, ask which to resume.\n5. Follow the selected task's existing plan. Add a required missing plan before coding.\n6. Implement and verify the remaining work.\n7. Condense the plan, move the task to Done, add a top `.tasks/WORK_LOG.md` entry when present, and update `CHANGELOG.md` when required.\n\nNever change task IDs or modify unrelated task sections.\n"

AFTER

"---\r\nname: continue-task\r\ndescription: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.\r\n---\r\n\r\n# Continue an In-Progress TaskPlanner Task\r\n\r\n1. Run the sibling `taskplanner` skill's version preflight once.\r\n2. Prefer `taskplanner_list` for In Progress and `taskplanner_get` for details, passing the absolute repository as `workspace_root`.\r\n3. If MCP cannot access the repository, read the In Progress file from the state mapping in `.tasks/config.json` and parse complete task sections directly.\r\n4. If none exist, suggest `next-task`; if several exist, ask which to resume.\r\n5. Follow the selected task's existing plan. Add a required missing plan before coding.\r\n6. Implement and verify the remaining work.\r\n7. Condense the plan, move the task to Done, add a top `.tasks/WORK_LOG.md` entry when present, and update `CHANGELOG.md` when required.\r\n\r\nNever change task IDs or modify unrelated task sections.\r\n"

Full snapshot data

{
  "description": "Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.",
  "included_files": [],
  "name": "continue-task",
  "skill_md_contents": "---\r\nname: continue-task\r\ndescription: Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.\r\n---\r\n\r\n# Continue an In-Progress TaskPlanner Task\r\n\r\n1. Run the sibling `taskplanner` skill's version preflight once.\r\n2. Prefer `taskplanner_list` for In Progress and `taskplanner_get` for details, passing the absolute repository as `workspace_root`.\r\n3. If MCP cannot access the repository, read the In Progress file from the state mapping in `.tasks/config.json` and parse complete task sections directly.\r\n4. If none exist, suggest `next-task`; if several exist, ask which to resume.\r\n5. Follow the selected task's existing plan. Add a required missing plan before coding.\r\n6. Implement and verify the remaining work.\r\n7. Condense the plan, move the task to Done, add a top `.tasks/WORK_LOG.md` entry when present, and update `CHANGELOG.md` when required.\r\n\r\nNever change task IDs or modify unrelated task sections.\r\n"
}

SHA-256 of public snapshot: 254e7259d8604c2ea4eb05a67415aeb5a675a507d2b1cbba3c4d74819735334d