Back to Details

todo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/todo

/todo

Turn the user's message into a Plane work item.
Default to a short 
interview
before creating the Plane item so the issue is specific, scoped, and actionable. Only skip the interview when the user clearly wants a fast inbox capture or provides a fully formed issue already.
将用户的消息转换为Plane工作项。
创建Plane工作项前默认先进行简短的
interview
，确保问题具体、范围明确且可执行。仅当用户明确需要快速收件箱捕获，或者已经提供了完整成型的问题时才跳过访谈步骤。

Behavior

行为规则

  • Default label: 
    claw_inbox
  • Extract (best effort):
    • due date (convert to YYYY-MM-DD)
    • priority (urgent/high/medium/low/none)
  • By default, use the 
    interview
    skill before creating anything.
  • Skip the interview only if:
    • the user explicitly wants a quick capture with minimal ceremony, or
    • the request already includes a solid title, scope, outcome, and next step
  • If you skip the interview and critical info is still missing, ask at most one clarifying question. If you still do not have enough detail, create it with 
    Needs details
    in the description.
  • 默认标签：
    claw_inbox
  • （尽力）提取以下信息：
    • 截止日期（转换为YYYY-MM-DD格式）
    • 优先级（urgent/high/medium/low/none）
  • 默认情况下，创建任何内容前先使用
    interview
    技能。
  • 仅在以下场景跳过访谈：
    • 用户明确需要极简流程快速捕获，或者
    • 请求已经包含了完善的标题、范围、产出和下一步动作
  • 如果跳过访谈后仍缺少关键信息，最多询问一个澄清问题。如果仍然没有足够细节，则创建任务时在描述中注明
    Needs details
    。

When to use 
interview

何时使用
interview

Use 
interview
as the default path. It is especially important when:
  • the input sounds like a problem to explore rather than a task to track
  • there is no clear outcome or deliverable
  • scope, owner, or next step is unclear
  • the user is asking to "flesh out", "think through", or define the issue
  • the title would otherwise be generic and the description would be mostly placeholders
When you use 
interview
:
  • keep it lightweight and focused on making one good Plane issue
  • ask enough questions to capture:
    • the problem or opportunity
    • the desired outcome
    • the scope and notable constraints
    • the next step or acceptance signal
  • then turn the resulting brief/spec into the Plane issue description
  • do not create the Plane item until the issue is concrete enough to be useful
默认路径为使用
interview
，在以下场景下尤其重要：
  • 输入听起来像是需要探索的问题，而不是需要跟踪的任务
  • 没有明确的产出或交付物
  • 范围、负责人或下一步动作不明确
  • 用户要求「flesh out」、「think through」或定义问题
  • 否则标题会过于通用，描述大部分都是占位符
使用
interview
时：
  • 保持轻量，专注于生成一个合格的Plane问题
  • 询问足够的问题以捕获：
    • 问题或机会点
    • 预期产出
    • 范围和值得注意的约束条件
    • 下一步动作或验收标准
  • 然后将得到的概要/规范转换为Plane问题描述
  • 直到问题足够具体可用时，再创建Plane工作项

Tool use

工具使用

  • By default, use the 
    interview
    skill first to produce a concise issue brief.
  • If you skip the interview, do so intentionally and only for fast capture or already-complete issues.
  • Use the 
    plane-api
    skill:
    • action: "create"
    • title: from the user, or from the refined issue brief if 
      interview
      was used
    • description: include the refined brief when available
    • due/priority if detected
    • labels: ["claw_inbox"]
  • 默认情况下，首先使用
    interview
    技能生成简洁的问题概要。
  • 如果你跳过访谈，必须是有意为之，且仅用于快速捕获或已经完整的问题。
  • 使用
    plane-api
    技能：
    • 动作："create"
    • 标题：来自用户输入，如果使用了
      interview
      则来自优化后的问题概要
    • 描述：如果有优化后的概要则包含在内
    • 截止日期/优先级（如果检测到）
    • 标签：["claw_inbox"]

Output

输出

  • ✅ Created: <title>
  • ID: <id>
  • Link: <url> (if available)
  • Briefly mention whether the issue was fleshed out via 
    interview
    or captured directly.
  • If failure: short error summary + what to fix (auth/base url/workspace/project).
  • ✅ 已创建：<title>
  • ID：<id>
  • 链接：<url>（如果可用）
  • 简要说明该问题是通过
    interview
    完善的还是直接捕获的。
  • 如果创建失败：简短的错误摘要 + 修复方案（鉴权/基础地址/工作区/项目）。