Plan next wave of GitHub work
github-next-wave-orchestratorskillsetup L2★0
Sheshiyer/skill-clusters ↗What it does
Analyze repo state and orchestrate next wave of work
Best for
Delivery orchestration from stalled or high-context repositories where a human decision-maker needs status + prioritized next batch to review
Inputs
- · [object Object]
- · [object Object]
- · [object Object]
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · GitHub API (gh CLI for issues, PRs, commits, CI checks)
- · Conductor integration (swarm-architect, copilot-swe-agent, ship-battery.mjs, loop-feedback.mjs)
Preconditions
Access to GitHub repo; knowledge of repo's issue/PR conventions and CI setup; optional: access to conductor for multi-agent dispatch
Failure modes
- · Fabricating repo state without querying GitHub
- · Incomplete evidence for priority ranking
- · Closing/merging without explicit user approval
- · Assuming repo has open issues when it may be idle
Trust signals
- · Readiness Score explicitly Green/Yellow/Red with thresholds (CI passing, P0 issues, commit recency)
- · Ranking rule balances unblocking, P0 fixes, and high-impact reversible work
- · Phase structure (Reality Scan, Synthesis, Design, Dispatch, Review)
- · Conductor integration documented (swarm-architect plan → parallel agents → ship-battery gate → loop-feedback close)
- · Guardrails: no fabrication, explicit approval gate for PR merges/issue close