메뉴
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.
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.
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.
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.
| name | taskplanner |
| description | 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. |
This workspace includes an MCP server named taskplanner plus an interactive MCP App board UI.
taskplanner_board_visual to open the kanban board.
taskplanner_move).taskplanner_get).TaskPlanner stores tasks as markdown files under .tasks/:
| State | File |
|---|---|
| Backlog | BACKLOG.md |
| Next | NEXT.md |
| In Progress | IN_PROGRESS.md |
| Done | DONE.md |
| Rejected | REJECTED.md |
Auxiliary: Work Log → WORK_LOG.md (rolling log of decisions and outcomes when tasks complete).
Each task is a ## section separated by ---.
taskplanner_board — board overview (counts; optional listings)\n+- taskplanner_list — list tasks (by state; optional query)\n+- taskplanner_get — get a task by ID\n+- taskplanner_create — create a new task (auto ID)\n+- taskplanner_move — move a task to another state\n+- taskplanner_update — update title/description/priority/tags/assignee/plan\n+- taskplanner_board_data — JSON board data (used by the UI)\n+- taskplanner_board_visual — open the interactive board (MCP App)\n+taskplanner_move).### Plan section under the task heading in IN_PROGRESS.md before coding (keep it 3–7 bullets).taskplanner_move).### Plan to a short done-summary..tasks/WORK_LOG.md if that file exists (newest at top).CHANGELOG.md entry under ## [Unreleased].