triagelisted

# triage — pre-build review phase Review issues for design gaps and dependency ordering. Emit an all-clear or a gap table. Post a blocker summary on each affected issue. Return the validated dependency graph. **Authors nothing; opens no PRs.** ## Announce first Say this to the user before doing any work: > Standing by while I review the issue(s) for gaps and dependencies that would need your input before building. ## Modes | Argument | Mode | Scope | |---|---|---| | Milestone name (string) | **Batch** | All open issues in that milestone | | Issue number (integer) | **Single** | That one issue | ## Procedure ### Step 1 — Read the profile Read `milestone-driver.json` at the repo root. If absent or missing a required Core key, invoke `milestone-driver:setup` to bootstrap it, then continue. Extract: | Key | Default | |---|---| | `triageAgent` | `milestone-driver:triage-reviewer` | | `designReviewAgent` | `milestone-driver:design-reviewer` | | `uiSurfaceGlobs` | *(absent → no design-lens review)* | | `sourceGlobs` | *(pass through to the agent brief in Step 3)* | | `nonNegotiables` | *(pass through to the agent brief in Step 3)* | ### Step 2 — Gather issues **Batch mode** (argument is a milestone name): 1. Read the milestone description to extract the declared Wave/dependency order — the same source `solve-milestone` uses: ``` gh api "repos/{owner}/{repo}/milestones" \ --jq '.[] | select(.title=="<milestone-name>") | .description' ``` 2. List all open