roadmap-orchestrator

Dispatches ready roadmap packages, gates PRs through CI and hardware tests, and writes daily standups.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a multi-package software roadmap by hand means constantly checking which packages are ready, spawning implementer agents, babysitting PRs through CI and hardware gates, and remembering to merge and clean up. This Skill automates one bounded orchestration tick so the roadmap advances on a cron schedule without manual supervision. ## Core Features & Use Cases - Bounded tick execution: Each invocation runs one guarded cycle — compute eligible packages, dispatch implementers into isolated git worktrees, route fixers for failing PRs, and exit — with a lock preventing overlapping ticks. - Dual-gate PR merging: PRs merge only when CI passes AND a hardware (GPU/CUDA) verification job bound to the PR's head SHA reports PASS, with independent different-model sign-off required for fixes and non-hardware-gated packages. - Standup and ledger automation: Every tick updates a daily standup document, records dispatch outcomes in a JSON ledger, and safely garbage-collects worktrees of merged PRs. - Use Case: A Windows Task Scheduler job fires every 10 minutes, invoking this Skill to dispatch the next ready renderer package to an implementer agent, read back a finished hardware test result, merge a green PR, and refresh the team standup — all without human input. ## Quick Start Run the roadmap-orchestrator skill with --dry-run to preview the dispatch, fixer, and merge plan for the current tick without any side effects.

Frequently Asked Questions about roadmap-orchestrator

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

FAQPage Schema
How do I automate roadmap package dispatch with AI agents?▼

Run one bounded orchestration tick that computes eligible packages from a next-stage report, then dispatches each to an implementer agent in its own isolated git worktree. A cron or Windows Task Scheduler job provides recurrence; the skill itself never loops in-session.

How do I gate PR merges on hardware GPU test results?▼

Bind the hardware verification job to the PR's head SHA and serialize it behind a GPU lock so exactly one CUDA job runs at a time. Auto-merge proceeds only when CI is all-pass and the hardware result recorded for the current head SHA is PASS.

Can I preview the orchestration plan without side effects?▼

Yes, run the skill with --dry-run. It prints the dispatch, fixer, hardware, and merge plan plus the standup text, then exits without acquiring locks, spawning agents, merging, or writing files.

What happens when a hardware verification test fails?▼

A hardware FAIL blocks the merge and dispatches a gate-failure-reviewer that produces a root-cause analysis and routes a fresh implementer to draft a fix. The fix is never pushed for re-gate without a recorded different-model SIGN-OFF verdict.

Why does the orchestrator skip dispatching a package?▼

Packages are skipped if they are research-only, have unmerged dependencies, an open PR, an active worktree, or a non-terminal dispatch outcome already recorded in the ledger. This prevents re-dispatching work already in flight.

When are agent worktrees deleted after PR merges?▼

Worktrees are removed only when the PR is MERGED on GitHub, its content is in origin/main (squash-aware), and the worktree has zero uncommitted or unpushed changes. Ambiguous cases are escalated as standup action items, never force-deleted.