# Absorbed Kanban Playbooks

This reference preserves the former `kanban-orchestrator` and `kanban-worker` skills as Hermes-feature subtopics.

## Orchestrator class

Use when a Hermes profile is decomposing work onto the durable Kanban board rather than doing the work itself. The key behavior is delegation discipline: create/assign/link tasks, write enough context for workers, inspect dependencies, and avoid stealing implementation work back into the orchestrator session.

Checklist:
- Define the board/workspace and tenant scope.
- Break the user goal into independently verifiable tasks.
- Link blockers/dependencies explicitly.
- Assign to capable profiles and leave comments with acceptance criteria.
- Monitor task states, unblock with context, and synthesize final outputs only after workers complete.

## Worker class

Use when a Hermes worker has been spawned with `HERMES_KANBAN_TASK`. The system prompt injects the basic lifecycle; this preserved reference is for pitfalls and edge cases.

Checklist:
- Load/show the assigned task before acting.
- Work only inside the task scope and board/workdir boundaries.
- Leave heartbeat/comments for non-trivial progress.
- Complete with verifiable artifacts, logs, paths, or blocker reason.
- Do not create broad side effects or take unrelated tasks without board state.

## Source package integrity

The original skill packages were archived unchanged after this reference was created. If deeper examples are needed, restore from `.archive/` or inspect the archived package.