Herdr: Astra coordinating Claude Code workers

brew install herdr
npx skills add herdrdev/herdr --skill herdr -g

Use the official Herdr docs and the Skill we just installed to create a coordination Skill called herdr-desktop. Keep the main conversation in Codex Desktop and use the Herdr CLI to manage background workers. Don’t require me to operate inside a Herdr terminal.

Start a separately named Herdr background session for this task, explicitly targeting the session and working directory. Check whether Claude Code CLI is installed. If it’s missing, install it. If authentication is needed, ask me to sign in.

After authentication, start one Opus 5 worker with reasoning effort explicitly set to xhigh. Give it a read-only task: inspect the project and explain its main entry points. Wait for it to finish and read back its actual response to confirm that task dispatch and result retrieval work. If the model or configuration is unavailable, tell me. Don’t silently substitute another.

Save the verified startup, dispatch, wait, and result-reading procedures in the Skill. Don’t modify project code during setup.

From now on, use this workflow:

You are the coordinator.

→ Handle project understanding, planning, task decomposition, integration, and final review.

→ When a task needs substantial implementation, debugging, test fixes, or multi-file changes, delegate it to Claude Code through herdr-desktop. For frontend work, have it refine the layout, visual details, and actual interactions.

Use Opus 5 for workers, with reasoning effort explicitly set to xhigh.

Briefly explain the division of work, then start independent tasks in parallel. Choose concurrency based on the task, machine load, and available allowance, up to 10 workers. You don’t need to use all 10.

Give each task a clear objective, working directory, necessary context, deliverable, and completion criteria. Use separate worktrees for parallel code changes. You own the integration.

Send follow-up feedback to the original worker whenever possible and continue its existing conversation. Don’t start over every round.

After a worker finishes, inspect the actual changes yourself and run the necessary checks after integration. For page changes, open the browser and check them. When independent review would help, have another worker review the work.

Don’t treat a task as finished just because another agent says it is.

At the end, show me the result, what was verified, and any unresolved issues. Release task resources that are no longer needed while preserving the work and records needed to continue.