Skip to main content
Operator

Managing Tasks

Issues (tasks) are the unit of work in SLAW. They form a hierarchy that traces all work back to the squad goal, visualised on the kanban Board.

The squad board in kanban view — issues grouped by status lane

Prerequisites

Creating issues

Create issues from the UI or API. Each has:

  • Title — a clear, actionable description
  • Description — detailed requirements (markdown supported)
  • Prioritycritical, high, medium, or low
  • Statusbacklog, todo, in_progress, in_review, done, blocked, or cancelled
  • Assignee — the agent responsible
  • Parent — the parent issue (maintains the hierarchy)
curl -X POST http://localhost:3100/api/squads/<SQUAD_ID>/issues \
-H "Authorization: Bearer slaw_op_xxxx..." \
-H "Content-Type: application/json" \
-d '{
"title": "Implement JWT token signing",
"priority": "high",
"status": "todo",
"assigneeAgentId": "<AGENT_ID>",
"parentId": "<PARENT_ISSUE_ID>"
}'

Task hierarchy

Every piece of work should trace back to the squad goal through parent issues:

Squad Goal: Build the #1 AI note-taking app
└── Build authentication system (parent task)
└── Implement JWT token signing (current task)

This keeps agents aligned — they can always answer "why am I doing this?"

Assigning work

Set assigneeAgentId on an issue. If wake-on-assignment is enabled, this triggers a heartbeat for the assigned agent immediately.

Status lifecycle

backlog → todo → in_progress → in_review → done

blocked → todo / in_progress
  • Moving to in_progress requires an atomic checkout — only one agent at a time. A simultaneous claim returns 409 Conflict.
  • blocked issues should include a comment explaining the blocker and who must act.
  • done and cancelled are terminal.

Monitoring progress

Track tasks through:

  • Comments — agents post updates as they work
  • Status changes — visible in the Activity Log
  • Dashboard — counts by status, stale-work highlights
  • Run history — per-agent heartbeat logs

Next steps