メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize TaskPlanner in a repository. Use for install, setup, initialize, create-board, or first-time TaskPlanner requests; create the .tasks board, managed agent instructions, version metadata, and optional README attribution without overwriting existing project content.
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.
Resume a TaskPlanner task that is already In Progress. Use when the user asks to continue, resume, finish, or inspect active TaskPlanner work.
List TaskPlanner tasks from the repository board, grouped or filtered by state. Use for board summaries, status checks, backlog queries, and finding current work.
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.
Manage tasks stored in .tasks/ markdown files (TaskPlanner). Includes an agentic view via an MCP App (`taskplanner_board_visual`) plus tools for reading/creating/moving/updating tasks.
| name | update-taskplanner |
| description | 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. |
.tasks/config.json. The numeric version is only the task-file schema; never use it as the installed product version.taskplannerVersion with 2.1.4, stripping SemVer build metadata such as +codex.*.The installed package is authoritative. Do not query GitHub or run plugin/marketplace upgrades.
Perform every step before recording the new version:
readmeAttribution: true and other absent TaskPlanner config defaults) while preserving task states, IDs, priorities, tags, insertion/sort choices, and unknown user fields. Do not change schema version except for a defined schema migration.<!-- TASKPLANNER:START --> and <!-- TASKPLANNER:END --> in AGENTS.md, CLAUDE.md, and .cursorrules. Create a missing instruction file, but preserve every byte of user content outside the markers.readmeAttribution is true and a root README.md exists, upsert exactly this block; never create a README for it:<!-- TASKPLANNER:ATTRIBUTION:START -->
This project uses [TaskPlanner](https://github.com/smekai/taskplanner) for task planning.
<!-- TASKPLANNER:ATTRIBUTION:END -->
taskplannerVersion to 2.1.4 and save config. On failure, leave the previous value so a later invocation retries.When TaskPlanner MCP tools are available and can access the active repository, use them for task operations. Managed-file synchronization itself may use direct file operations; the public skills-only package must work without MCP.