skills.rest
Powerworks
PowerworksCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-slice-status

Updates a slice's status field on an eventmodelers board via the node events API.

1|1|Updated Jul 19, 2026
Search Tags:#concurrency#event modeling#curl#board api#eventmodelers#slice status#codegen workflow
One-click install
npx skills add https://github.com/Powerworks/K9DatingApp --skill update-slice-status-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-slice-status
Source: https://github.com/Powerworks/K9DatingApp/tree/main/.claude/skills/update-slice-status
Command: npx skills add https://github.com/Powerworks/K9DatingApp --skill update-slice-status-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents or developers work through slices on an eventmodelers.ai board, slice statuses must be updated programmatically to reflect progress. This Skill changes a single slice's status by sending a node:changed event to the board API, eliminating manual board edits during automated codegen workflows. ## Core Features & Use Cases - Status Transition by Name: Finds a slice by case-insensitive title match and updates its sliceStatus field to values like InProgress, Review, or Done. - Concurrency Guard Handling: Detects when the API rejects an update because another agent already claimed the slice, reporting a distinct ALREADY_IN_STATUS outcome instead of a generic error. - Use Case: A Ralph loop build agent claims a Planned slice by moving it to InProgress before generating code; if another agent got there first, it receives ALREADY_IN_STATUS and picks a different slice. ## Quick Start Ask the assistant to update the slice named "Order Placed" to status InProgress on the connected eventmodelers board.

Frequently Asked Questions about update-slice-status

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

FAQPage Schema
How do I update a slice status on an eventmodelers board?▼

Provide the slice title and target status; the skill lists all slices via the board API, matches the title case-insensitively, then posts a node:changed event with the new sliceStatus value to the nodes events endpoint.

What status values are valid for eventmodelers slices?▼

Valid statuses are Created, Planned, InProgress, Review, Done, Blocked, Assigned, and Informational. Values are case-sensitive, and the skill stops with the list of options if an invalid status is given.

Why does the slice status update fail with an already-in-status error?▼

The API rejects moving a slice into a status it already holds as a concurrency guard against racing agents. The skill reports this as ALREADY_IN_STATUS, signaling callers to pick a different slice rather than retrying.

What happens if the slice name is not found on the board?▼

The skill stops and lists all available slice titles from the board so you can select the correct one. Matching is case-insensitive but requires an actual title match.

Does this skill work without board credentials configured?▼

No. It requires TOKEN, BOARD_ID, ORG_ID, and BASE_URL, which it obtains by invoking the connect skill first. It will not proceed until the connect skill completes successfully.

Related Skills

Explore More Software Engineering Skills→
PowerworksPowerworks
1

load-slice

Fetches event-modeling slices from the slicedata API and persists them to local directories.

Community
Intermediate
fcnatrafcnatra

event-modeling

Design software systems using Event Modeling with vertical slices.

Community
Advanced
PowerworksPowerworks

wdyt

Analyzes event model slices and posts business questions as board comments.

Community
Intermediate
AgentiveStackAgentiveStack
71

tdd

Implement features using test-driven development with public interface tests.

Official
Intermediate