wo-update

Update WO files, backlog, and sprint boards during lifecycle transitions.

Updated Aug 23, 2026

Search Tags:#workflow #backlog #lifecycle #sprint-board #work-order #wo-update

Ready to run

npx skills add https://github.com/mattfuster/aisef-setup --skill wo-update

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wo-update
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/wo-update
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill wo-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update work orders and keep all hub artifacts in sync across WO files, backlog, and sprint boards to ensure consistent lifecycle tracking.

Core Features & Use Cases

Orchestrates WO status transitions (backlog, ready, in_progress, in_review, blocked, completed) and updates all related artifacts.
Enforces cross-artifact consistency and facilitates collaboration with wo-create and wo-review.
Provides guardrails to prompt for necessary delivery details and approvals before progressing to final states.

Quick Start

Tell the agent to move a WO to the desired status, for example, WO-123 is in_progress.

Frequently Asked Questions about wo-update

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

FAQPage Schema

How do I update work order status and keep my backlog synchronized?▼

To update work order status and keep your backlog synchronized, this Skill orchestrates WO lifecycle transitions and automatically updates WO files, backlog items, and sprint boards in a single coordinated action.

Can I move a work order to completed without filling out the Delivery section?▼

You cannot move a work order to completed without filling out the Delivery section. The enforces cross-artifact consistency and requires completing the Delivery section for impl-repo work before progressing to final states.

What work order lifecycle states are supported for sprint board transitions?▼

The work order lifecycle states supported for sprint board transitions include backlog, ready, in_progress, in_review, blocked, and completed. These statuses are applicable across both manual and automated workflows.

How do I mark a work order as blocked and ensure the sprint board reflects it?▼

To mark a work order as blocked and ensure the sprint board reflects it, tell the agent to move the WO to the blocked status. The Skill will synchronize the WO file, backlog, and sprint board automatically.

Does this work order lifecycle tool require any external dependencies?▼

This work order lifecycle tool does not require any external dependencies. It operates independently to coordinate WO files, backlogs, and sprint boards without needing additional components or packages.

What's the best way to coordinate work order creation, updates, and reviews?▼

The best way to coordinate work order creation, updates, and reviews is using this Skill alongside wo-create and wo-review. It facilitates collaboration with these tools to provide full lifecycle coverage and cross-artifact consistency.