← ClaudeAtlas

crowsnest-dispatchlisted

Hand a corpus of work to a Claude Code session instead of doing it yourself. Use when the watching (crowsnest) session is asked to start work somewhere, when a conversation about one project has run on long enough that it belongs in that project's own session, or when an existing session should be given the next thing to do. Triggers on: 'start a session in X to do Y', 'get someone working on this', 'have X do the next issue', 'spin up a session for', 'tell the parser session to', 'hand this off', 'who should do this', 'take this over to that repo'. Covers naming, the brief, spawning, subscribing to the finish, and recording the dispatch.
thorwhalen/crowsnest · ★ 0 · Data & Documents · score 66
Install: claude install-skill thorwhalen/crowsnest
# crowsnest-dispatch — handing a corpus of work to a session You do not do corpus work. When work needs doing, a session in that working directory does it, and you go back to watching. This is how you hand it over. **The one thing to get right:** the brief is *pointers*, not prose. Everything you retype into a brief is context you paid for twice and that the session cannot verify. Give it URLs and paths and let it read them. ## 1. Does a session already exist for this corpus? Run `crowsnest` (or ask the scout) and look for a live session in that working directory. - **One is there and `idle`** → message it. No new session. - **One is there and `busy`** → queue nothing. Either wait for the idle notice, or tell the user it is mid-turn and ask whether to interrupt it. - **One is there and `waiting`** → it needs its human, not more work. Tell the user what it is waiting for; that is the blocker. - **None** → spawn one. **One session per corpus.** A second session on the same repository is allowed only in its own git worktree, on a disjoint set of files, and only when the split is written into both briefs. Parallel workers on the same files make conflicting implicit decisions that nobody sees until the merge. ## 2. Name it The name is the address for everything afterwards — the roster row, `crowsnest show`, `SendMessage`, and its ledger file. Pick a short, unique, lowercase one that says the corpus and the job: `parser-tests`, `tw-deploy-fix`, `cn-ledger`. Never reuse