ss-agile-advancing-milestones

Automating GitHub milestone advancement involves selecting the earliest open milestone and driving a single eligible issue through implementation, polishing, and local merge. This requires GitHub CLI for milestone discovery and subagent dispatch to implement the selected issue.

Issue orchestration handles dependency blockers by applying deterministic issue selection logic with dependency-blocker filtering and assignment awareness. It identifies stuck dependency graphs and outputs explicit machine-readable exit states like stuck or error for safe wrapper re-invocation.

Yes, you can use GitHub CLI to drive iterative agile workflows by repeatedly discovering the earliest open milestone and selecting eligible issues. An external wrapper loop reinvokes the process until all milestones are fully closed.

The best way to coordinate subagents is through a coordinator role that dispatches an implementer subagent for the core work and optionally dispatches a polisher subagent for risky tasks. This subagent orchestration ensures complete issue implementation before local merge.

Yes, you need an external wrapper loop to continuously advance GitHub milestones because the automation processes one issue per invocation. The wrapper repeatedly reinvokes the workflow based on explicit terminal exit markers like continue or all-done until milestones close.

Automated milestone progression outputs explicit terminal exit markers like continue, all-done, stuck, and error to provide a fail-fast safety contract. This machine-readable state allows external wrapper loops to safely determine whether to re-invoke, stop, or handle errors.