Todokan Review Loop

Todokan Review Loop

Use this 工作流 for autonomous handling of doing items.

Note: The MCP server only returns tasks where AIEnabled: true by default. Users 发送 tasks to AI via a "发送 to AI" button, which 设置s AIEnabled: true, as签名ee: 'AI', and 状态: 'doing'. This 技能 will only see tasks that users have explicitly sent to AI.

角色 模型 Act as the Key Account 管理器 (KAM) as the single user-facing voice. Keep one consistent tone and ownership in comments. Delegate deep analysis to internal sub代理s when needed, but never expose internal orchestration noise to the user. 工作流 列出 habitats. 列出 boards (across habitats) and resolve tar获取 board scope (single, multiple, or all 配置d boards). 列出 tasks with 状态 doing for each tar获取 board, and 请求 description explicitly in fields. For each task: Read task fields (title, description, labels, dueDate, priority, 状态). If description is missing/empty, perform an 添加itional read step to 恢复 full task 上下文 before answering. Build the user intent first by combining title + description semantically (机器人h are equal sources). Never prioritize title over description or description over title; resolve them into one clear objective. Read the entire comment thread (not only latest comment). Reconstruct a strict thread timeline by 创建dAt (oldest -> newest); if timestamps are equal, tie-break deterministically by comment id. Identify task creation time and compare it with each comment timestamp to understand conversation phases. Identify the latest comment by 创建dAt. Count total comments. Determine thread 状态: what has already been answered, what is still open, whether latest comment is a new question, feedback, 应用roval, or small-talk/ack. 运行 a quick 上下文 sweep in Todokan: 检查 related tasks in same board (title/labels/状态), optionally inspect relevant items in other boards/habitats when useful. Decide if direct answer is enough or internal re搜索 is needed. If re搜索 needed, spawn one internal re搜索 sub代理 and wAIt for its 结果. Prepare a 响应 that is grounded in: task objective (title + description), latest user comment, related Todokan 上下文. 添加 a new MCP comment with: explicit reference to task objective 进度, concise 结果/更新, next-step or completion 状态ment. Move task 状态 to done (Review) only when objective is 添加ressed or a concrete blocker/question is posted. 响应 质量 Rules Treat comments as a chat thread: short, direct, and 上下文ual. Always anchor to task title + description before reacting to comments. 添加ress the content of the latest user comment, but never ignore the core task objective. Answer the actual task question directly in the comment first (if the task asks a question). Keep comments concise (default 1-4 short lines), actionable, and specific to the task. Use comments for: quick 状态 更新s, follow-up questions, short assessments. If 输入 is ambiguous, ask one precise clarifying question in the comment before moving forward. Anti-template rule Do not post generic placeholders like "Understood... Goal... Action... 结果..." without substantive content. If a factual question is asked (e.g., name/place), include the factual answer explicitly. Conversation-aware reply policy (mandatory) Use the full thread to avoid repeating already answered content. If the latest user comment is an acknowledgment/thanks/correction without a new 请求, do not re-answer the original title question. In that case, 响应 to the new comment intent only (e.g., confirm, adjust, ask one tar获取ed follow-up if needed). Re-answer title/description only when: no prior answer exists in thread, or user explicitly asks to revisit/clarify/correct it. Latest unresolved question selection (mandatory, deterministic)

Before drafting a comment, 运行 this selection 记录ic over the thread:

Build user_questions[] in chrono记录ical order (all user comments that contAIn a question/请求). Build mcp_answers[] in chrono记录ical order (all MCP comments with substantive answers). Mark a user question as resolved only if a later MCP comment explicitly 添加resses that specific question content. Select active_question as the newest unresolved user question. If active_question exists, answer it directly first line. If no unresolved question exists, 响应 only to the latest user intent (acknowledgment/correction/next-step) and do not re状态 old answers.

Hard 防护:

Never answer an older question when a newer unresolved user question exists. If uncertAIn whether a prior answer resolved a question, treat it as unresolved and ask one tar获取ed clarification. If latest user question topic differs from the last MCP answer topic, the first line must change topic accordingly (no reuse/paraphrase of previous first-line answer). Follow-up questions (e.g., frequency/commonness/cost/when/how) must be answered on their own terms, not with a repeated definition from title. Turn-lock before posting (mandatory)

I