一键导入
todo-workflow
Step-by-step task tracking via the TODO_WRITE marker. Use when executing any multi-step task, follow-up request, or build workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Step-by-step task tracking via the TODO_WRITE marker. Use when executing any multi-step task, follow-up request, or build workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Batch project dependency changes and install once. Use when starting a new feature, scaffolding a project, or when any npm/pnpm package installation is needed.
Pre-planning procedure for new tasks. Visualize end state, identify structure, and anticipate problems before coding. Use when starting a new feature, scaffolding a project, or planning a multi-file change.
Fix-verify iteration loop for dependency, build, and runtime errors. Use when installing packages, running dev servers, fixing build errors, or verifying that code compiles and runs.
Concise output formatting for the Hatchway platform UI. Use when generating any response during task execution.
Read-before-write discipline. Search for patterns and understand existing code before modifying files. Use when editing existing files, adding features to an existing codebase, or creating new components.
Visual design thinking for production-ready UI. Use when building new pages, components, or styling any user-facing interface.
| name | todo-workflow |
| description | Step-by-step task tracking via the TODO_WRITE marker. Use when executing any multi-step task, follow-up request, or build workflow. |
| user-invocable | false |
The Hatchway UI shows build progress as a checklist. You drive that checklist by
emitting a TODO_WRITE: marker in your normal assistant text — not by
calling a tool. Do not use TodoWrite, TaskCreate, TaskUpdate, or
TaskList for progress tracking — the UI does not render those, and they are
unreliable in this environment. The UI renders progress only from the
TODO_WRITE: marker. If you never emit it, the user sees nothing happening.
Write a line that begins with TODO_WRITE: followed by one JSON object holding
the full todo list (always include every item with its current status):
TODO_WRITE: {"todos":[{"content":"Short task name","status":"in_progress","activeForm":"Doing the task"}]}
Rules:
status is exactly one of: "pending", "in_progress", "completed".in_progress, the rest pending.in_progress item.completed and the next in_progress.completed.Update after every single item — never batch multiple completions into one marker.
Task: "Add a dark mode toggle"
TODO_WRITE: {"todos":[{"content":"Add theme context","status":"in_progress","activeForm":"Adding theme context"},{"content":"Add toggle to header","status":"pending","activeForm":"Adding toggle to header"}]}
(create ThemeContext.tsx)
TODO_WRITE: {"todos":[{"content":"Add theme context","status":"completed","activeForm":"Adding theme context"},{"content":"Add toggle to header","status":"in_progress","activeForm":"Adding toggle to header"}]}
(create DarkModeToggle.tsx, add to Header)
TODO_WRITE: {"todos":[{"content":"Add theme context","status":"completed","activeForm":"Adding theme context"},{"content":"Add toggle to header","status":"completed","activeForm":"Adding toggle to header"}]}
Even simple follow-up requests get at least one todo. Emit it in_progress, do
the work, then emit it completed.
Keep working until 100% complete. Do not pause to ask "Should I continue?" unless you need information only the user can provide or encounter an unrecoverable error.