القائمة
Update the status of a single slice on an eventmodelers board by changing the SLICE_BORDER node's sliceStatus field
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | update-slice-status |
| description | Update the status of a single slice on an eventmodelers board by changing the SLICE_BORDER node's sliceStatus field |
Before doing anything else, invoke the
connectskill to resolveTOKEN,BOARD_ID,ORG_ID, andBASE_URL. Do not proceed until the connect skill has completed.
From $ARGUMENTS, extract:
| Field | How to find it | Default |
|---|---|---|
sliceName | the slice title to update (case-insensitive match) | required |
newStatus | the target status value | required |
Valid status values (case-sensitive):
| Value | Meaning |
|---|---|
Created | Default — slice has been created but not started |
Planned | Work is planned |
InProgress | Work is actively in progress |
Review | Ready for review |
Done | Completed |
Blocked | Blocked by something |
Assigned | Assigned to someone |
Informational | Informational / reference slice |
If newStatus is not one of these exact values, stop and tell the user the valid options.
Fetch all slices on the board:
curl -s \
-H "x-token: <TOKEN>" \
-H "x-board-id: <BOARD_ID>" \
-H "x-user-id: update-slice-status-skill" \
"<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/slicedata/slices"
Response: { "slices": [{ "id": "<nodeId>", "title": "<title>", "status": "<status>" }] }
The id here is the SLICE_BORDER node ID — use it directly in Step 3.
Find the slice whose title matches sliceName (case-insensitive). If no match is found, stop and list the available slice titles so the user can pick one.
Save the matched slice as:
SLICE_NODE_ID — the node ID of the SLICE_BORDERCURRENT_STATUS — the current status valueSend a node:changed event to update the sliceStatus field in the SLICE_BORDER node's meta:
curl -s -X POST "<BASE_URL>/api/org/<ORG_ID>/boards/<BOARD_ID>/nodes/events" \
-H "Content-Type: application/json" \
-H "x-token: <TOKEN>" \
-H "x-board-id: <BOARD_ID>" \
-H "x-user-id: update-slice-status-skill" \
-d '[{
"id": "<new-random-uuid>",
"eventType": "node:changed",
"nodeId": "<SLICE_NODE_ID>",
"boardId": "<BOARD_ID>",
"timestamp": <Date.now()>,
"changedAttributes": ["sliceStatus"],
"meta": {
"sliceStatus": "<newStatus>"
}
}]'
Response: { "hashes": { "<eventId>": "<hash>" } }
Tell the user:
CURRENT_STATUSnewStatusSLICE_NODE_IDExample success output:
Updated: "Order Placed" slice
Before: InProgress
After: Done
Node ID: a1b2c3d4-…
Teaches an agent everything about the eventmodelers platform API — all endpoints, their purpose, request payloads, response shapes, authentication, and element types.
Implements an emmett state-view slice (projection, tests, route, migration) from a slice.json definition
Teaches an agent everything about the eventmodelers platform API — all endpoints, their purpose, request payloads, response shapes, authentication, and element types.
Teaches an agent everything about the eventmodelers platform API — all endpoints, their purpose, request payloads, response shapes, authentication, and element types.
Implement automation and translation slices the Cratis way — an IReactor that observes events and produces side effects, triggering further writes via ICommandPipeline. Use when: (1) implementing a new automation / reactor in a Cratis project, (2) a slice.json has a non-empty processors[] section or sliceType === "TRANSLATION", (3) the user provides an Event Modeling artifact or description of an event-driven reaction and asks to implement it, (4) the user says "implement", "create", "add" an automation, reactor, translation, or event-to-command flow in a Cratis Arc / Chronicle project.
Implement Event Sourcing write slices the Cratis way — using Cratis Arc (CQRS) + Cratis Chronicle (event sourcing) in a .NET / C# project. A write slice is: Command → Handle() → Event(s), with optional validators, constraints, and DCB business rules. Use when: (1) implementing a new write slice / command in a Cratis project, (2) a slice.json has a non-empty commands[] / events[] section, (3) the user provides an Event Modeling artifact, specification, or natural-language description of a command and asks to implement it, (4) the user says "implement", "create", "add" a write slice, command, or state change in a Cratis Arc / Chronicle project.