← TaskPlannerCONTENT HISTORY

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

Skill instructions — Now says: --- name: next-task description: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or...

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: next-task description: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task. --- # Start the Next TaskPlanner Task 1. Run th...

After

Nov 9, 2026 · 12:07 UTC

--- name: next-task description: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task. --- # Start the Next TaskPlanner Task 1....

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,16 +1,16 @@
----
-name: next-task
-description: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.
----
-
-# Start the Next TaskPlanner Task
-
-1. Run the sibling `taskplanner` skill's version preflight once.
-2. Prefer `taskplanner_list` for Next, then Backlog, always passing the absolute repository as `workspace_root`. If MCP cannot access the repository, read and parse the configured state files directly.
-3. Select the highest priority task and identify it to the user.
-4. Move its complete section to In Progress with `taskplanner_move` or a direct cut/insert.
-5. Read `.tasks/config.json`; when `aiPlanRequired` is true, add a concise `### Plan` before coding.
-6. Implement and verify the task.
-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: next-task
+description: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.
+---
+
+# Start the Next TaskPlanner Task
+
+1. Run the sibling `taskplanner` skill's version preflight once.
+2. Prefer `taskplanner_list` for Next, then Backlog, always passing the absolute repository as `workspace_root`. If MCP cannot access the repository, read and parse the configured state files directly.
+3. Select the highest priority task and identify it to the user.
+4. Move its complete section to In Progress with `taskplanner_move` or a direct cut/insert.
+5. Read `.tasks/config.json`; when `aiPlanRequired` is true, add a concise `### Plan` before coding.
+6. Implement and verify the task.
+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: next-task\ndescription: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.\n---\n\n# Start the Next TaskPlanner Task\n\n1. Run the sibling `taskplanner` skill's version preflight once.\n2. Prefer `taskplanner_list` for Next, then Backlog, always passing the absolute repository as `workspace_root`. If MCP cannot access the repository, read and parse the configured state files directly.\n3. Select the highest priority task and identify it to the user.\n4. Move its complete section to In Progress with `taskplanner_move` or a direct cut/insert.\n5. Read `.tasks/config.json`; when `aiPlanRequired` is true, add a concise `### Plan` before coding.\n6. Implement and verify the task.\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: next-task\r\ndescription: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.\r\n---\r\n\r\n# Start the Next TaskPlanner Task\r\n\r\n1. Run the sibling `taskplanner` skill's version preflight once.\r\n2. Prefer `taskplanner_list` for Next, then Backlog, always passing the absolute repository as `workspace_root`. If MCP cannot access the repository, read and parse the configured state files directly.\r\n3. Select the highest priority task and identify it to the user.\r\n4. Move its complete section to In Progress with `taskplanner_move` or a direct cut/insert.\r\n5. Read `.tasks/config.json`; when `aiPlanRequired` is true, add a concise `### Plan` before coding.\r\n6. Implement and verify the task.\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": "Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.",
  "included_files": [],
  "name": "next-task",
  "skill_md_contents": "---\r\nname: next-task\r\ndescription: Select and implement the highest-priority TaskPlanner task from Next or Backlog. Use when the user asks to start, pick, or complete the next planned task.\r\n---\r\n\r\n# Start the Next TaskPlanner Task\r\n\r\n1. Run the sibling `taskplanner` skill's version preflight once.\r\n2. Prefer `taskplanner_list` for Next, then Backlog, always passing the absolute repository as `workspace_root`. If MCP cannot access the repository, read and parse the configured state files directly.\r\n3. Select the highest priority task and identify it to the user.\r\n4. Move its complete section to In Progress with `taskplanner_move` or a direct cut/insert.\r\n5. Read `.tasks/config.json`; when `aiPlanRequired` is true, add a concise `### Plan` before coding.\r\n6. Implement and verify the task.\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: 7b727f76a0efb68debb852dbb69479382a38d31033ef030f5f5e163fbf4fd499