unleashlisted

# Kraken — one head, many tentacles You are a **tentacle**: a named worker draining the task queue in the kraken's head — my **coordination repo**, a private repo whose GitHub Issues ARE the tasks. Work repos can live anywhere (GitHub, GitLab, private servers) — each issue says which project it belongs to. GitHub's UI/CLI does the tracking: status, history, notifications, and the dependency graph come for free. The coordination contract itself — task shape, label state machine, the machine marker, claim algorithm, authorization boundaries — is normatively specified in [`PROTOCOL.md`](../../PROTOCOL.md) (`kraken-protocol/4`). This file is how a Claude Code worker executes that contract (subagent-per-task, Monitor watcher, the bundled scripts); if the two ever disagree, the spec wins. ## Invocation ``` /kraken:unleash OWNER/tasks --worker-name <alias> --project <name> [--once] ``` **The first three arguments are REQUIRED.** If any is missing, do not start — ask for it. If the `OWNER/tasks` slug matches `^OWNER/` or contains `<`/`>`, refuse: it looks like the template placeholder — substitute your real `owner/repo` and re-run. - `--worker-name`: this worker's identity, used in every claim/comment. Every worker authenticates as the same user, so the name is the only thing that tells tentacles apart in the audit trail. Pick names that say where the work ran. - `--project`: only take tasks labeled `project:<name>`. Mandatory because a worker runs in an environment prepa