skills.rest
AllBeingsFuture
AllBeingsFutureCOMMUNITY
Explore all skills by this author →
GitHub

update-plan-step

Update a plan step's status with validated step_id and structured output.

9|2|Updated Mar 18, 2026
Search Tags:#workflow#status#plan#update#tracking#step
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill update-plan-step-allbeingsfuture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-plan-step
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/system/update-plan-step
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill update-plan-step-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step status updates are often missed, making it hard to track progress across a multi-step plan. This skill enforces timely status updates after completing each step to keep the overall workflow transparent and auditable.

Core Features & Use Cases

  • Update a plan step status (pending, in_progress, completed, failed, or skipped) to reflect real progress.
  • Validate required inputs (step_id and status) and attach an optional result message for context.
  • Integrate with plan orchestration to produce a consistent, auditable trail of task execution across teams.

Quick Start

Tell the system to update a plan step, e.g., set step_id 'step_1' to 'completed' with a brief result.

Frequently Asked Questions about update-plan-step

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

FAQPage Schema
How do I update the status of a workflow step to keep my plan tracking accurate?▼

To update a workflow step status, you provide a step_id and a status value such as pending, in_progress, completed, failed, or skipped. This enforces timely progress tracking and creates an auditable trail across teams.

What information is required to track plan progress after completing a step?▼

Tracking plan progress requires the step_id and the new status field. You can also include an optional result message to attach additional context to the status update payload for better workflow transparency.

Can I attach context or results when I mark a plan step as completed or failed?▼

Yes, when marking a plan step as completed or failed, you can include an optional result message. This attaches context to the structured payload, keeping the multi-step workflow execution transparent and auditable.

What step statuses are supported for tracking progress in a multi-step plan?▼

Supported step statuses for tracking plan progress include pending, in_progress, completed, failed, and skipped. Validating these specific statuses ensures consistent task execution tracking across teams.

Why does my multi-step workflow lose transparency across teams during execution?▼

Multi-step workflows lose transparency when step status updates are missed after completion. Enforcing structured status updates with a step_id and status ensures progress is tracked accurately and maintains an auditable trail.

Do I need a separate orchestration tool to maintain an auditable trail of task execution?▼

You do not need a separate tool to maintain an auditable trail if you integrate this status update process with your plan orchestration. It produces a consistent, structured payload tracking task execution across teams automatically.

Related Skills

Explore More Product & Management Skills→
guifryguifry

ads-plan

Create a complete Google Ads plan covering economics, structure, budget, bidding, and targeting.

Community
Advanced
rockandrolla13rockandrolla13

plan-tracker

Create, update, and verify PLAN-*.md files for multi-step workflows.

Community
Advanced
cqkxxccqkxxc

dispatching-parallel-agents

Coordinate parallel agents to investigate independent problems concurrently.

Community
Intermediate
jin-bojin-bo
94

kanban-tasks

Break down feature requirements into atomic task cards with acceptance criteria.

Community
Advanced