kanban-workflows

Topics in the source

• Kanban Workflows
• Overview
• When to Use
• Orchestrator Role
• Worker Role
• Card Content Template
• Summary and Metadata Shapes
• Heartbeats and Notifications

This is the class-level skill for board operations. It merges the former orchestrator and worker skills into one lifecycle playbook: when to use the board, how to decompose work, how workers should claim/execute/report, and how to recover stuck work. The basic worker lifecycle may be auto-injected by runtime guidance. Load this skill when you need the deeper operational playbook or need to reason across orchestrator and worker roles. Commands below use board kanban … as the entry point; substitute your board implementation's own binary name. The subcommands, flags and quirks are the part this skill is written against. The task is larger than one agent turn and benefits from persistent cards. Multiple workers/profiles/tools should run concurrently. A user asks for status, decomposition, stuck-worker recovery, or board-process debugging. You are acting as an orchestrator and must avoid doing the work yourself. You are a worker and need concrete summary/metadata/blocking patterns. Do not use the board for a single simple edit/search/action that the current agent can finish immediately. Also skip the board for uniform batch fan-out — dozens of near-identical runs of one shape (e.g. the

This is an excerpt. Refer to the complete source and its current requirements.