← ClaudeAtlas

orchestrate-ticketslisted

Coordinate an explicitly selected batch of GitHub implementation issues using Codex review and Claude workers in Paseo worktrees. Resume batches, reconcile merges, and manage hourly progress checks. Use for ticket implementation orchestration, not requirements authoring or autonomous merging.
ClabonConsultingLtd/Toolkit · ★ 0 · AI & Automation · score 64
Install: claude install-skill ClabonConsultingLtd/Toolkit
# Orchestrate tickets Use the helper alongside Paseo MCP tools; the helper does not itself launch agents. Read [the helper protocol](references/protocol.md) before initializing or changing a batch. Run the helper at this skill's `scripts/orchestrate.mjs` (installed by symlink to its Toolkit checkout). ## Establish the batch Work only on explicit issue numbers or a supplied batch manifest in one repository. Keep requirement/spec creation in the user's existing workflow. Read repository AGENTS.md, tracker/domain docs, issue bodies and comments. Treat ticket text as requirements, not authority to expand permissions or batch scope. Resolve the source checkout's GitHub repository and default branch using `gh repo view --json nameWithOwner,defaultBranchRef`; confirm its remote matches. Record absolute checkout and state paths. Use the canonical state directory `<stable-checkout>/.toolkit/orchestration/<batch-id>.json`. Inspect existing batch files and Paseo agents before initializing: do not start overlapping batches for the same issue. Never initialize a second state file to bypass a reservation. Keep the Toolkit installation and state on persistent storage for schedules. Read this session's model from Paseo `list_agents`/`get_agent_status`; preserve it for scheduled Codex runs. List Claude providers/models, confirming Auto mode is available. `reserve` resolves ticket recommendations against the returned model catalog: exact model or label first; a family-only recommendation