auto-work-milestone

Work Milestone - Process All Issues in a Milestone

Process all open issues in a specific GitHub milestone using context-isolated subagents.

Usage

/auto-work-milestone {milestone_number}

Workflow Mode

WORKFLOW_MODE: milestone
AUTO_MERGE: true (handled by this orchestrator after /auto-work-issue completes)

---

Instructions

You are the Milestone Implementation Orchestrator. You:

1. Validate the milestone exists and get its details
2. List all open issues in the milestone
3. Select issues based on dependencies and priority
4. Spawn /auto-work-issue {n} as a subagent for each issue (context isolation)
5. Parse subagent output to determine result
6. Merge successful PRs
7. Enforce circuit breaker limits
8. Report milestone-specific progress

---

Load Context

1. Load the workflow-orchestration skill
2. Load the github-workflow skill
3. Check for implementation-plan.md (if exists, filter to milestone issues and follow order)
4. Read circuit breaker limits from .claude/settings.json under automatasaurus.limits

---

Validate Milestone

Before starting, validate the milestone exists:

# Get milestone info
gh api repos/:owner/:repo/milestones/$ARGUMENTS --jq '{title: .title, open_issues: .open_issues, description: .description}'

If milestone doesn't exist or has no open issues, report and exit:

• Invalid milestone number → Error: "Milestone #X not found"
• No open issues → Success: "Milestone #X ({title}) has no open issues"

Store milestone info:

MILESTONE_NUMBER = $ARGUMENTS
MILESTONE_TITLE = [from API response]
MILESTONE_TOTAL = [open_issues from API response]

---

Circuit Breaker Limits

Before each iteration, check limits from settings:

Limit	Default	Action When Exceeded
maxIssuesPerRun	20	Stop, report progress
maxEscalationsBeforeStop	3	Stop, notify human
maxConsecutiveFailures	3	Stop, notify human

Initialize counters:

issuesProcessed = 0
escalationCount = 0
consecutiveFailures = 0
successCount = 0
blockedCount = 0