dispatch-next

Routes the highest-priority open package from the stage report to the correct implementation agent.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill dispatch-next-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatch-next
Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/dispatch-next
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill dispatch-next-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-package development in the Astroray renderer requires manually reading planning reports, checking which packages already have open PRs or worktrees, and deciding which agent should implement each package. This Skill automates that triage and dispatch step. ## Core Features & Use Cases - Priority Selection: Reads NEXT_STAGE_REPORT.md section 2 and picks the top-priority open package not already in flight. - Cost-Aware Routing: Applies a tier check to decide whether a package qualifies for open-model delegation via the delegate skill or should go to the package-implementer agent. - Worktree Dispatch: Spawns the chosen agent in a fresh git worktree with the verbatim drop-in prompt, package spec path, and worktree name. - Dry-Run Mode: Supports --dry-run to print the routing decision without spawning any agent. - Use Case: After a planning round completes, run /dispatch-next to automatically hand off the next package (e.g., pkg55 Phase B) to the right agent with the correct prompt and worktree. ## Quick Start Run /dispatch-next to read the current stage report and dispatch the top-priority open package to the appropriate agent in a new worktree.

Frequently Asked Questions about dispatch-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dispatch the next package to an implementation agent?▼

Run /dispatch-next, which reads NEXT_STAGE_REPORT.md section 2, finds the highest-priority open package without an open PR or active worktree, and spawns the appropriate agent in a fresh git worktree with the verbatim drop-in prompt.

How does the skill decide between delegate and package-implementer agents?▼

It applies a tier check: well-specified small fixes with crisp acceptance criteria and no novel physics or ABI changes qualify for open-model delegation via the delegate skill. Novel algorithms, BSDF or light-transport math, and ABI-touching changes route to package-implementer.

Can I preview the routing decision without spawning an agent?▼

Yes, invoke the skill with --dry-run. It prints the routing decision including package name, chosen agent, and worktree name without creating a worktree or spawning any agent.

What happens if a package already has an open PR or worktree?▼

The skill skips that package and moves to the next highest-priority open package in the recommended deployable set, ensuring work is never duplicated across agents.

When should a package not be delegated to an open-weight model?▼

Avoid delegation for novel algorithm integration, ambiguous specs, BSDF/integrator/light-transport math, and ABI-touching header changes. When in doubt, route to the package-implementer agent instead.