mcp-todo

MCP Server TODO Management

This skill teaches an agent to query and mutate MCP Server TODO items through the plugin (workflow.todo.*) instead of touching storage files. In this workspace, "TODO" always means an MCP Server TODO item: not Claude Code's in-session task list, not a markdown checklist, and not a GitHub issue list.

When to Use

• The user says: "list todos", "open TODOs", "create a todo", "update todo", "mark todo done", "check todo status", "plan implementation", "query tasks".
• You need the current TODO backlog, a single TODO by id, or to record progress on an item you are implementing.
• You discover work that must be tracked as a persisted TODO.

When Not to Use

• Tracking ephemeral, in-session steps for yourself: use the harness task list, not MCP TODOs.
• Session logging, requirements (FR/TR), or GraphRAG operations: those are separate plugin surfaces (workflow.sessionlog.*, requirements docs, GraphRAG), not workflow.todo.*.
• Any time the only goal is to read docs/Project/TODO.yaml "quickly". That is still forbidden; use workflow.todo.query / workflow.todo.get.

Inputs

• A TODO id for get/select/update/delete (canonical format, see Critical Rules).
• For query: optional filters keyword, priority (critical|high|medium|low), section, and done (boolean).
• For create: required id, title, section, priority; optional estimate, description (string array), technicalDetails, implementationTasks ({task, done}), note, remaining, dependsOn, functionalRequirements, technicalRequirements.
• For update: id plus only the fields you want to change (same shape as create, plus done, completedDate, doneSummary).

Critical Rules

1. NEVER read or write TODO.yaml, docs/Project/TODO.yaml, or any TODO storage file directly with Read, Edit, Write, Grep, or shell cat. The plugin is the only allowed interface. A "quick lookup" is still a violation.
2. Route every operation through the Claude Code plugin (mcpserver-claude-code-plugin) using workflow.todo.* methods. "Not in the visible tool list" does not mean unavailable; use the documented wrapper form.
3. Persisted TODO ids must match ^[A-Z][A-Z0-9]*(?:-[A-Z0-9]+)+-\d{3}$ (uppercase kebab-case, three-digit suffix) or ^ISSUE-\d+$. Valid: PLAN-NAMINGCONVENTIONS-001, MCP-TODO-CREATE-001, ISSUE-17. Invalid: plan-api-001, MCP-API-42, MCP-001, ISSUE-ABC.
4. To create a GitHub-backed TODO, submit the special id ISSUE-NEW. The server creates the issue, rewrites the saved id to the canonical ISSUE-{number}, and returns that id. After first sync, ISSUE-{number} descriptions are immutable; updates surface to GitHub as a comment, not a body rewrite.
5. Each dependsOn entry must itself be a valid persisted TODO id.
6. Do not invent methods or fields. The only TODO methods are listed in Workflow.
7. Every request needs a unique requestId, format req-<yyyyMMddTHHmmssZ>-<seq-or-slug>, unique within the session.