Closes a development round by updating docs and triggering strategy reviews.
npx skills add https://github.com/HendrikGC02/Astroray --skill close-round-hendrikgc02
Please help me install this Agent Skill. Skill: close-round Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/close-round Command: npx skills add https://github.com/HendrikGC02/Astroray --skill close-round-hendrikgc02
gh pr view, and blocks the closeout until specs are flipped to done. - Docs-updater orchestration: Spawns the docs-updater agent with the list of PRs merged since the last STATUS.md update and confirms the doc PR is open or merged. - Strategy review trigger: Evaluates conditions (deferred targets, rounds since last review) and spawns the architect agent in state+refine mode when warranted. - Use Case: After merging several renderer packages, run the closeout to flip spec statuses, regenerate status docs, and get a summary of what the next dispatch will pick up. ## Quick Start Run /close-round after the round's PRs are merged to update the docs and check whether a strategy review should fire.High-intent search queries and answers about installing and using this skill.
Invoke /close-round after the round's PRs are merged. It audits spec statuses, spawns the docs-updater agent to refresh STATUS.md, checks whether an architect strategy review is due, and reports what the next dispatch will pick up.
The gate greps all specs under .astroray_plan/packages/ for statuses still reading pending or in review. For each hit naming a PR, it runs gh pr view to check the PR state; if merged or closed, the closeout fails until the spec is flipped to done.
An architect state+refine pass fires when three or more packages have deferred targets, when it is the third round since the last review, or as a light pass every round. The light pass reads current render output and status, then asks one short question.
The closeout fails if a spec still reads pending or in-review while its referenced PR is merged or closed. Flip the spec status to done with the PR number, date, and headline numbers, then rerun the closeout.
No. It only verifies PR states through the GitHub CLI and coordinates the docs-updater and architect agents. Merging is handled separately by the pr-merger, which also flips specs at merge time.
auerbachbGenerate a consolidated PR dashboard with review state, findings, and blockers.
win4rCoordinate multi-agent development pipelines by managing tasks, statuses, and agent dispatch.
Botool-Dev-TeamResume stopped TestBench sessions from the last completed round.
Codagent-AIGenerate lightweight planning artifacts for small code changes.