Todokan

Todokan — Kanban Task Management

Todokan is a kanban-style task 管理器. You can manage the user's tasks, boards, and projects through MCP 工具s.

Prerequisites A Todokan MCP server must be avAIlable (see README for 设置up) Required env vars: TODOKAN_API_KEY, TODOKAN_MCP_URL (declared in 技能 metadata) Trigger — When to Activate This 技能

Activate the Todokan 技能 when the user has one of the following intents:

Intent Example 创建 / edit / 删除 a task "创建 a task: review PR" Show boards or tasks "Show me my tasks", "What's on the dev board?" Change 状态 "Mark task X as done" Save re搜索 结果s "Save this as a task / document in Todokan" Briefing / summary from tasks "Give me a briefing of my open tasks" Attach a document to a task "Write a note on task X" 搜索 topics across boards "What did I note about the investor meeting?" Retrieve changes since last 检查 "What's new since this morning?"

Do not activate when the user is just talking about tasks in general without referencing Todokan.

工具 Ordering

Follow this order to achieve consistent 结果s:

Reading (always orient first)

• 列出_habitats → Which workspaces exist?
• 列出_boards → Which boards exist? (note the IDs)
• 列出_tasks → Tasks on a board (with 过滤器s)
• 搜索_across_habitats → Full-text 搜索 across boards/habitats
• 获取_事件_since → Retrieve changes since a timestamp
• 列出_board_labels → AvAIlable labels + usage counts
• 列出_task_documents → Documents attached to a task
• read_document → Content of a document

Writing (only after orientation + confirmation)

• 创建_task / 创建_board / 创建_habitat
• 更新_task / 更新_task_by_title
• 创建_document / 添加_document_to_task
• 删除_task → Only after explicit confirmation

AI-Assisted (optional)

• propose_task_variants → 生成 2-3 variants
• confirm_task_fields → Review fields before creation

Golden rule: Never write blindly. Always call 列出_boards first to discover IDs — never guess UUIDs.

Mandatory 检查s

Before executing write actions, clarify the following:

Before 创建_task Board: Which board? (If unclear → show 列出_boards, let the user choose) Title: Short, precise, imperative (max 80 characters) Priority: low / normal / high — default to normal if unclear Due date: Only 设置 if mentioned by the user Before 更新_task Correct task? 状态 the title + board for confirmation Which fields? Only change the fields the user 请求ed Before 删除_task Always ask for explicit confirmation — "Should I permanently 删除 task '[Title]' on board '[Board]'? This cannot be undone." Before 创建_document Clarify 格式化: markdown, text, or html Link: Attach to which task (or standalone)? 防护rAIls No Hallucination Use only real data from MCP 工具 响应s. Never fabricate task IDs, board names, or content. If a 工具 call fAIls or returns empty data: 信息rm the user, do not improvise. When in doubt, show the actual 结果s and ask. No Sensitive Data Do not store passwords, API keys, 令牌s, or personal data in task titles or descriptions. If the user mentions sensitive in格式化ion, warn them: "This may contAIn sensitive data — should I really store it in Todokan?" Source Attribution When storing content from external re搜索 (网页, files, other 工具s) in Todokan, note the source in the task description or document: Source: [URL or filename] 创建d by: 代理 on [date]

Scope Awareness Worker 端点 (/mcp-worker): Read-only + comments (添加_comment). No task/board CUD, no document creation. Planner 端点 (/mcp): Full 访问. Still ask before destructive actions. On scope errors: explAIn to the user that the current 端点 does not have the required 权限s. Idempotency On network errors: do not blindly retry the same action. First 检查 whether the action was already performed (列出_tasks). 输出 格式化 Briefing (summary of existing tasks)

Briefing: [Board Name] — [Date]

Open (todo): X tasks In 进度 (doing): Y tasks Completed (done): Z tasks

Urgent (high priority)

• [ ] [Task Title] — due [Date]
• [ ] [Task Title] — due [Date]

In 进度

• [~] [Task Title] — since [Date]

Next Steps

Draft (preview before task creation)

Task Draft

Document Draft

Document Draft

Title: [Title] 格式化: markdown Linked to: [Task Title] on [Board Name]

Should I cr