一键导入
potatoupdate-task-status
Use this skill to update the status of an existing task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use this skill to update the status of an existing task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to add comments or notes to an existing task. Comments help track progress, document decisions, or explain issues.
You MUST use this anytime you want to ask the user a question or feel like something is unclear. If you think you want to use the AskUserQuestion tool, first invoke this skill, we may have a different way of asking the user a question.
You MUST use this skill in order to create, update, edit, or build artifacts or files. Artifacts can be of any type but are typically markdown files.
Use this skill to create a new task for tracking work within the current ticket. Tasks help break down work into smaller trackable units.
Use this skill to create a new ticket in the current project. Use this to convert a brainstorm into a formal ticket for tracking development work.
Use this skill to retrieve details of a specific task by its ID. Returns the task's description, status, comments, and other metadata.
| name | potato:update-task-status |
| description | Use this skill to update the status of an existing task. |
Update task status BEFORE and AFTER every work block. Starting work? Set in_progress first. Finished? Set completed immediately. No silent work.
update_task_status({
taskId: "task1",
status: "in_progress",
});
| Status | When to Use |
|---|---|
pending | Task created but not started |
in_progress | Actively working on the task |
completed | Task finished successfully |
| When... | Do this IMMEDIATELY |
|---|---|
| You start working on a task | update_task_status({ taskId, status: "in_progress" }) |
| You finish a task successfully | update_task_status({ taskId, status: "completed" }) |
| You switch to a different task | Update the old task, then update the new task |
These thoughts mean you're rationalizing:
| Excuse | Reality |
|---|---|
| "I'll update it when I'm done" | Update NOW. You might forget or get interrupted. |
| "It's obvious I'm working on it" | Nothing is obvious without explicit status. |
| "This is a quick task, no need" | Quick tasks still need tracking. Always update. |
| "I'll batch my status updates" | Status updates are real-time. Update immediately. |
// BEFORE starting work - required
update_task_status({ taskId: "task1", status: "in_progress" });
// ... do the work ...
// AFTER completing work - required
update_task_status({ taskId: "task1", status: "completed" });
Tasks without status updates = invisible work. Invisible work = wasted effort when sessions end unexpectedly.