skills/codex/todo-list-csv/SKILL.md
当需要修改项目(增删改文件)并希望将 update_plan 与 CSV 有机同步时使用此技能:在项目根目录创建“{任务名} TO DO list.csv”,用 TODO/IN_PROGRESS/DONE 驱动 plan 的 pending/in_progress/completed,同步推进,全部完成后删除该文件。
npx skillsauth add lili-luo/aicoding-cookbook todo-list-csvInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
在需要修改项目时,用一个位于项目根目录的 CSV 文件把工作拆成可勾选的步骤;在推进过程中持续更新;全部完成后删除该 CSV,避免把临时清单遗留或提交进仓库。
update_plan 建立计划并在执行过程中持续更新。update_plan 建立初始 plan:第 1 步 in_progress,其余 pending。step 文案与 CSV 的 item 完全一致(便于同步与审计)。{任务名} TO DO list.csv{任务名} TO DO list.csv。CSV 表头固定为(首行):
id,item,status,done_at,notes
id:从 1 开始的整数item:单条待办(与 plan 的 step 一致)status:TODO / IN_PROGRESS / DONEdone_at:完成时间(ISO 8601,未完成留空)notes:可选备注(文件路径、验证方式、PR/commit 等)TODO → IN_PROGRESS → DONE(避免 TODO 直跳 DONE)。TODO→pending,IN_PROGRESS→in_progress,DONE→completed。IN_PROGRESS;只要仍有未完成项,尽量保持 恰好 1 行 IN_PROGRESS(与 plan 的唯一 in_progress 对齐)。IN_PROGRESS 项后:
advance 自动“完成当前项并启动下一项”)plan --normalize)update_plan 使 plan 与 CSV 同步in_progress,或追加“等待反馈”步骤并置为 in_progress。DONE,再删除该 CSV 文件(脚本 cleanup 会在未全 DONE 时拒绝删除)。update_plan 将所有步骤标记为 completed,确保对话内计划闭环。使用 scripts/todo_csv.py 自动创建/更新/清理 CSV(优先用于避免手工编辑出错)。
示例命令:
python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py init --title "修复登录 bug" --item "复现问题" "加回归测试" "修复实现" "运行测试/构建"python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py path --title "修复登录 bug"update_plan payload(推荐带 --normalize):python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py plan --file "{csv_path}" --normalize --explanation "同步自 TODO CSV"python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py start --file "{csv_path}" --id 2python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py advance --file "{csv_path}" --notes "已通过单测"python3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py status --file "{csv_path}" --verbosepython3 ~/.codex/skills/todo-list-csv/scripts/todo_csv.py cleanup --file "{csv_path}"development
Unified task execution protocol for Codex-only work. Supports Single Task, Epic Task, and Batch Task while preserving CSV truth-source, validation gates, context recovery, and Debug-First failure exposure. WHEN TO USE: user asks to "track tasks", "create todo list", "make a plan", "track progress", "long task", "big project", "build from scratch", "autonomous session", "跟踪任务", "自主执行", "长时任务", "从零开始", "任务管理", "做个计划", "大工程", or when a task clearly requires 3+ ordered steps that produce file changes. DO NOT USE: single-step fixes, pure Q&A, code review, explaining code, search/research tasks, tasks with fewer than 3 steps, or tasks that do not produce file changes.
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------