一键导入
write-todos-skill
Create and manage structured task lists for planning and tracking complex multi-step operations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create and manage structured task lists for planning and tracking complex multi-step operations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to generate well-branded interfaces and assets for OpenCompany (zeenie.ai), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Launch Android applications by package name. Open any installed app programmatically.
Get list of installed Android applications with package names, versions, and metadata.
Control Android audio - get/set volume, mute/unmute for media, ringtone, notification, and call volumes.
Monitor Android device battery status, level, charging state, temperature, and health.
Control Android Bluetooth - enable, disable, get status, and list paired devices.
| name | write-todos-skill |
| description | Create and manage structured task lists for planning and tracking complex multi-step operations. |
| allowed-tools | write_todos |
| metadata | {"author":"opencompany","version":"2.0","category":"automation"} |
You have access to the write_todos tool. Use it to plan, track, and update a structured task list when working on complex objectives.
Use write_todos when the task requires 3 or more steps. Do NOT use it for trivial requests that you can complete in 1-2 tool calls.
Follow this loop for every complex task:
Before doing any work, call write_todos to create your plan. Break the objective into specific, actionable steps. Mark the first task in_progress immediately.
{
"todos": [
{"content": "Identify the relevant source files", "status": "in_progress"},
{"content": "Implement the core logic", "status": "pending"},
{"content": "Add error handling", "status": "pending"},
{"content": "Verify the changes work", "status": "pending"}
]
}
After completing a step, call write_todos again with the updated list. Mark the finished task completed and the next task in_progress. Do this after every step -- do not batch updates.
{
"todos": [
{"content": "Identify the relevant source files", "status": "completed"},
{"content": "Implement the core logic", "status": "in_progress"},
{"content": "Add error handling", "status": "pending"},
{"content": "Verify the changes work", "status": "pending"}
]
}
If you discover new work or a step becomes irrelevant, update the list. Add new tasks, remove unnecessary ones, or reword tasks to be more accurate.
{
"todos": [
{"content": "Identify the relevant source files", "status": "completed"},
{"content": "Implement the core logic", "status": "completed"},
{"content": "Fix unexpected edge case in parser", "status": "in_progress"},
{"content": "Add error handling", "status": "pending"},
{"content": "Verify the changes work", "status": "pending"}
]
}
Keep working until every task is completed. Always have at least one task in_progress unless all are done.
write_todos call per turn -- never call it multiple times in parallel.in_progress before starting a task, completed after finishing it.completed if there are unresolved errors or the work is partial.| Field | Type | Description |
|---|---|---|
| todos | array | Full list of todo items |
| todos[].content | string | Specific, actionable task description |
| todos[].status | string | pending, in_progress, or completed |