astroray-architect-round

Orchestrates autonomous Astroray renderer development rounds with package selection, delegation, and verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating an autonomous development round on the Astroray path tracer requires reading live planning documents, picking the right package, delegating bounded work, and verifying visual and engineering evidence before merging. This Skill encodes that architect-first workflow so a round runs consistently without manual orchestration. ## Core Features & Use Cases - Package Selection: Reads STATUS.md, NEXT_STAGE_REPORT.md, and ROADMAP.md plus git/GitHub state to exclude in-flight work and select the most valuable eligible package. - Bounded Delegation: Routes grunt tasks, well-specified implementation slices, and read-only pre-review through the astroray-opencode-delegator with dynamic model tiers, while keeping visual judgment and independent sign-off on separate high-tier lineages. - Evidence-Gated Delivery: Enforces documented gates, caller/binding sweeps, independent review, GPU-lock-serialized CUDA verification, and visual-check workflows before committing, pushing, opening the PR, and merging. - Use Case: Run an autonomous round on the Astroray renderer where the agent picks the next package (e.g., responsiveness/cancellation measurement), executes it in an isolated worktree, verifies renders visually, and ships the PR with updated planning docs. ## Quick Start Run an architect-first Astroray delivery round that selects the next eligible package, delegates bounded work, and verifies all evidence before merging.

Frequently Asked Questions about astroray-architect-round

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

FAQPage Schema
How do I run an autonomous development round on the Astroray renderer?▼

Invoke the architect round workflow, which reads AGENTS.md and the planning hierarchy (STATUS.md, NEXT_STAGE_REPORT.md, ROADMAP.md), selects the most valuable eligible package, executes it in an isolated worktree, and delivers after all gates pass.

How does the skill decide which package to work on next?▼

It uses the astroray-index plus current git and GitHub state to exclude in-flight work, then produces an architect decision covering dependencies, acceptance gates, risks, and whether a spec or research refresh is needed.

What kinds of tasks get delegated during a round?▼

Delegation covers grunt work like research indexing, docs, and mechanical hygiene, plus well-specified implementation slices in isolated worktrees and read-only pre-review. Visual judgment and independent sign-off are never delegated to text-only or same-lineage workers.

When does the workflow require owner input instead of proceeding autonomously?▼

Owner input is required for a material priority conflict, a pause directive, or a genuine scope change. Ordinary execution, including small independently verifiable tangents delegated as separate tasks, proceeds autonomously.

How are visual or spectral rendering changes verified before merging?▼

Representative output is saved and checked through the visual-check workflow in addition to numerical gates. CUDA-heavy build and render verification is serialized through a GPU lock, with at most two implementation worktrees active per round.