ship-batchworkflow★0
harennon/cardgamesimulator ↗What it does
Triage open issues in parallel, select and ship 2-3 autonomously
Best for
Autonomously grooming a backlog and shipping a prioritized batch end-to-end without human re-triage
Inputs
- · repository with open GitHub issues
Outputs
- · triage recommendation per issue {realProblem, effort, 11-point risk profile, recommendation}
- · selected batch of 2-3 issues
- · ship execution results per issue
Requires
- · gh CLI (authenticated)
- · agent orchestration (parallel triagers, CEO-model selector, sequential ship executors)
Preconditions
- · GitHub CLI authenticated
- · Repository has open issues
Failure modes
- · Issue triaged as 'fix' but ship-issue fails on unblocked dependency
- · CEO model selection misprioritizes (low effort but high blast-radius chosen)
- · Triage risk profile misses game-correctness dimension
Trust signals
- · 4-phase Triage → Label → Select (CEO/opus model) → Ship
- · 11-point risk taxonomy per issue (availability, scaling, ops, UX, compat, security, data, reversibility, blast radius, game correctness, testability)
- · Triage labels applied + comments posted on close/needs-info
- · Sequential ship execution