Verified:GitHub

update-todo-step

Updates the status of a plan step to track execution progress.

2.0k|274|Updated Jan 30, 2026

Search Tags:#agent workflow #progress tracking #status update #Todo #Plan #Task Management

One-click install

npx skills add https://github.com/openakita/openakita --skill update-todo-step

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: update-todo-step
Source: https://github.com/openakita/openakita/tree/main/skills/system/update-todo-step
Command: npx skills add https://github.com/openakita/openakita --skill update-todo-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an AI agent executes a multi-step plan, there is no visibility into which steps are done, in progress, or failed. This Skill records the status of each plan step so progress is tracked consistently after every action.

Core Features & Use Cases

Step Status Updates: Set any plan step to pending, in_progress, completed, failed, or skipped by its step ID.
Result Recording: Attach an execution result or error message to each status update for later review.
Use Case: While executing a browser automation plan, the agent marks step_1 as completed with the result "opened the homepage", then marks step_2 as failed with "search box element not found", so the plan handler can react accordingly.

Quick Start

After finishing a plan step, call update-todo-step with the step ID, the new status, and an optional result message.

Frequently Asked Questions about update-todo-step

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track progress of a multi-step agent plan?▼

Call update-todo-step after completing each step, passing the step_id and a status of pending, in_progress, completed, failed, or skipped. You can attach a result message describing the outcome or error.

What status values does the plan step update support?▼

The status parameter accepts five values: pending, in_progress, completed, failed, and skipped. Each update requires a step_id, and the result field is optional for recording execution details.

When should I call the step status update during plan execution?▼

It must be called after completing each step of the plan. This keeps the plan handler informed of progress so it can continue, retry, or abort based on step outcomes.

What happens if a plan step fails during execution?▼

Mark the step as failed and include the error details in the result field, such as a missing UI element. Related skills like get-todo-status can then be used to inspect the overall plan state.