Skill · em Planejar o trabalho

workspace-orchestration

Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots/ require an active claim.

Procedência

Antes de instalar

2 arquivos · 4,8 KB · só texto, nenhum script

Instalar na sua CLI

O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.

Claude Code

Neste projeto: instala em .claude/skills/workspace-orchestration/.

d=".claude/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Global: instala em ~/.claude/skills/workspace-orchestration/.

d="$HOME/.claude/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Codex

Neste projeto: instala em .agents/skills/workspace-orchestration/.

d=".agents/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Global: instala em ~/.agents/skills/workspace-orchestration/.

d="$HOME/.agents/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Antigravity

Neste projeto: instala em .agents/skills/workspace-orchestration/.

d=".agents/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Global: instala em ~/.gemini/antigravity-cli/skills/workspace-orchestration/.

d="$HOME/.gemini/antigravity-cli/skills/workspace-orchestration"
u="https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/skills/development/workspace-orchestration"
curl -fsSL --create-dirs \
  -o "$d/SKILL.md" "$u/SKILL.md" \
  -o "$d/LICENSE" "$u/LICENSE"

Peça ao Rook

Já usa o Rook Labs? Cole no chat do Rook: instale a skill https://rooklabs.sh/marketplace/cct.workspace-orchestration

Prévia do SKILL.md

---
name: workspace-orchestration
description: Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots/ require an active claim.
---

# 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:

- `/dock-status`
- `/dock-claim <slot> <branch> <task>`
- `/dock-heartbeat <slot>`
- `/dock-release <slot>`
- `/dock-doctor`

## Rules

- Work from the root. Edit code in `slots/*`.
- If `$DOCKO_SESSION_ID` is empty (plugin hooks not installed, or a different runtime), stop before the first claim and resolve a real session id — never run claim or heartbeat with an empty `--session`. Use `docko session list --brief` or `docko session current` to pick one.
- Never invent a session id. The PreToolUse hook checks the runtime's own session, so a made-up id claims a slot that then blocks your own writes. Use `$DOCKO_SESSION_ID`, or an id from `docko session list --brief`.
- `branch` is claim metadata. docko records it and never runs `git checkout`.
…

Ver todo o marketplace