docko Workspace Orchestration

Use this skill whenever work touches files in slots/ or when the user asks about workspace coordination.

Quick Path

1. Run /dock-status or docko status --brief. docko walks up to the workspace root on its own, so this works from inside a slot; pass --root <workspace> only from outside the workspace.
2. Pass --session "$DOCKO_SESSION_ID" on every claim, heartbeat, and release. The SessionStart hook exports it for this session.
3. Prefer docko slot acquire --session "$DOCKO_SESSION_ID" --branch <branch> --task "<task>" --brief when you want docko to pick a slot. Selection is round-robin, starting after the last slot claimed for that application.
4. In a workspace with several applications, pass --application <id> so the pick stays inside the right pool.
5. Add --prefer <slot-id> when a specific slot is the right one (it already has the branch, say). docko takes it when free and rotates normally when it is not.
6. If every slot is busy and docko asks whether it should create a fresh managed clone, answer explicitly.
7. Use docko claim --session "$DOCKO_SESSION_ID" --resource slot --id <slot> --branch <branch> --task "<task>" only when you already know the exact slot.
8. Do the work inside that slot. On long-running work, keep the claim fresh: docko heartbeat --session "$DOCKO_SESSION_ID" --resource slot --id <slot>
9. Release the slot when done: docko release --session "$DOCKO_SESSION_ID" --resource slot --id <slot>

Prefer slash commands when installed: