Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

deepagents-planning-todosDeepagents 计划待办事项

Agent Skill

deepagents-planning-todos 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

324

周安装

13

GitHub Stars

94

下载量

105
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:deepagents-planning-todos(Deepagents 计划待办事项)
来源仓库:https://github.com/lubu-labs/langchain-agent-skills
仓库路径:skills/deepagents-planning-todos
安装命令:
npx skills add https://github.com/lubu-labs/langchain-agent-skills --skill deepagents-planning-todos
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/lubu-labs/langchain-agent-skills --skill deepagents-planning-todos

简介

deepagents-planning-todos 提供 write_todos 工具用于 Deep Agents 中的有效任务规划与分解。

  • 适用于需要将三步以上复杂任务拆分为可跟踪子任务、展示执行计划或调试待办完成问题的场景。
  • 支持不同任务类型模板(研究/编码/分析/文档处理)与 LangSmith 追踪可视化集成。
  • 使用前需确认目标环境支持 LangChain 生态,并注意待办项需在 Deep Agents 上下文中执行。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Deep Agents Planning and Todos

Master the write_todos tool for effective task planning and decomposition in Deep Agents.

Use This Skill When

  • You need to break down complex multi-step tasks (3+ steps) into trackable subtasks.
  • You want to show users the plan before executing (user approval workflow).
  • You're debugging why todos aren't completing as expected.
  • You need patterns for different task types (research, coding, analysis, document processing).
  • You want to visualize todo progression from LangSmith traces.

When To Use write_todos

Use write_todosExecute Directly
✅ Complex multi-step tasks (3-6 steps)✅ Simple 1-2 step queries
✅ Tasks requiring user approval first✅ Single tool calls
✅ Long-running workflows needing progress tracking✅ Quick information lookups
✅ Tasks where planning adds clarity✅ Straightforward API calls

Decision rule: If you'd benefit from showing the user "Here's my plan..." before starting, use write_todos.

Quick Start

from deepagents import create_deep_agent

# TodoListMiddleware is included by default in create_deep_agent
agent = create_deep_agent(
    model="anthropic:claude-sonnet-4-5-20250929",
    tools=[search_tool, summarize_tool],
    system_prompt="You are a research assistant. Use write_todos for multi-step tasks."
)

# Agent workflow:
# 1. Call write_todos with initial plan
# 2. Ask user: "Does this plan look good?"
# 3. User approves → start executing
# 4. Update the todo list as work progresses
# 5. Keep todos aligned with the current plan and execution state

Example todo creation:

# Agent calls write_todos internally:
{
  "name": "write_todos",
  "arguments": {
    "todos": [
      {"content": "Search for papers on LLM agents", "status": "pending"},
      {"content": "Read and extract findings from top 5 papers", "status": "pending"},
      {"content": "Identify common themes", "status": "pending"},
      {"content": "Write summary report", "status": "pending"}
    ]
  }
}

Todo Structure and API

Two-Field Structure

{
  "content": "Task description (clear, actionable)",
  "status": "pending" | "in_progress" | "completed"
}

Key Constraints

Full-list updates: Treat each write_todos call as a full state update and include all active todos.

Per-turn discipline: Prefer one write_todos update per model turn to avoid conflicting plan changes.

Best granularity: Keep lists to 3-6 items maximum (avoid over-fragmentation).

Tooling Note

Deep Agents documentation describes write_todos as the built-in interface for todo planning/tracking. Keep todo state accurate by rewriting the list with updated statuses as execution progresses.

Status Lifecycle

pending → in_progress → completed

Best practices:

  1. Create todos with "status": "pending" for newly planned work.
  2. Update to "in_progress" when starting work on a todo.
  3. Mark "completed" when finished (don't delete - keeps context).
  4. For interactive workflows, ask user approval ("Does this plan look good?") before starting execution.

Typical workflow:

# Step 1: Create initial plan (all pending)
write_todos([
  {"content": "Research topic", "status": "pending"},
  {"content": "Write summary", "status": "pending"}
])

# Step 2: Ask user approval
# User: "Yes, proceed"

# Step 3: Start first task
write_todos([
  {"content": "Research topic", "status": "in_progress"},
  {"content": "Write summary", "status": "pending"}
])

# Step 4: Complete first task, start second
write_todos([
  {"content": "Research topic", "status": "completed"},
  {"content": "Write summary", "status": "in_progress"}
])

# Step 5: Finish all tasks
write_todos([
  {"content": "Research topic", "status": "completed"},
  {"content": "Write summary", "status": "completed"}
])

Todo Patterns By Task Type

Quick Reference

Task TypePatternExample Todos
Researchgather → synthesize → reportSearch docs, Read examples, Analyze patterns, Synthesize findings
Codingdesign → implement → testDesign API, Implement endpoints, Write tests, Test end-to-end
Analysiscollect → process → analyzeCollect data, Process traces, Analyze patterns, Visualize results
Document Processingread → extract → transformRead files, Extract key info, Transform format, Output result

For detailed patterns with code examples, see references/todo-patterns.md.

Best Practices

✅ DO

  • Granularity: Keep lists to 3-6 items max (clear milestones, not micro-tasks).
  • Naming: Use clear, action-oriented descriptions ("Search for X", "Analyze Y").
  • User interaction: Always ask approval before executing plan.
  • Status updates: Update promptly as items complete (don't skip status transitions).
  • Context management: Use with filesystem tools for complex workflows.

⚠️ DON'T

  • Over-fragment: Avoid 10+ todos (too granular, hard to track).
  • Vague descriptions: "Do research" → "Search LangChain docs for Deep Agents overview".
  • Skip approval: Don't start executing without user confirmation.
  • Forget updates: Always update status when transitioning tasks.
  • Drop existing context: Include existing active items when rewriting todos.

Troubleshooting

Todo Not Completing

Symptom: Todo stuck in in_progress, agent loops or gets confused.

Causes & fixes:

  • Missing status update → Ensure agent updates status when task finishes.
  • Unclear completion criteria → Make content more specific ("Read 5 papers" vs "Do research").
  • Agent forgot about todos → Add to system prompt: "Use write_todos to maintain and update the plan as work progresses."

Agent Ignoring Todos

Symptom: Agent creates todos but doesn't follow them.

Causes & fixes:

  • Missing system prompt guidance → Add: "Follow the todo list. Update status as you complete each item."
  • One-off task (doesn't need todos) → Use direct execution for simple queries.
  • Conflicting instructions → Remove competing planning instructions from prompt.

Too Many Todos

Symptom: 10+ todos, hard to track, agent overwhelmed.

Causes & fixes:

  • Over-planning → Simplify to 3-6 high-level milestones.
  • Nested subtasks → Use todo hierarchy pattern (see references/todo-patterns.md).
  • Wrong abstraction → Consider breaking into multiple agent invocations.

Lost Context

Symptom: Agent loses track of what's been done.

Causes & fixes:

  • No filesystem persistence → Use FilesystemBackend or StoreBackend for long sessions.
  • Not maintaining todos → Update write_todos whenever status changes or scope shifts.
  • Memory issues → Use MemoryMiddleware for long-term context.

Visualizing Todos

Use the included script to parse LangSmith traces and visualize todo progression:

# Export trace from LangSmith (download JSON)
# Then run:
uv run skills/deepagents-planning-todos/scripts/visualize_todos.py trace.json

# Show Mermaid diagram:
uv run skills/deepagents-planning-todos/scripts/visualize_todos.py trace.json --format mermaid

# Show full timeline:
uv run skills/deepagents-planning-todos/scripts/visualize_todos.py trace.json --show-timeline

Output example:

Todo Timeline for trace abc123:

Initial Plan (Step 1):
  ⏳ [pending] Search for papers on LLM agents
  ⏳ [pending] Read and extract findings
  ⏳ [pending] Identify common themes
  ⏳ [pending] Write summary report

Final State:
  ✅ [completed] Search for papers on LLM agents
  ✅ [completed] Read and extract findings
  ✅ [completed] Identify common themes
  ✅ [completed] Write summary report

Resources

References (detailed patterns):

  • references/todo-patterns.md: Task-specific patterns with code examples

Examples (working code):

  • assets/examples/todo-driven-agent/: Research agent demonstrating full workflow

Example structures (templates):

  • assets/todo-structures/research-todos.json: Research task breakdown
  • assets/todo-structures/coding-todos.json: Coding task breakdown

External docs:

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.31%
按下载量换算38

Claude

30.12%
按下载量换算32

Cursor

16.26%
按下载量换算17

Gemini CLI

8.23%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills