work-onlisted

@.claude/shirabe-extensions/work-on.md @.claude/shirabe-extensions/work-on.local.md # Feature Development Workflow Your goal is to work on a GitHub issue and deliver a high-quality, well-tested pull request. ## Input Resolution The input `$ARGUMENTS` can be an issue reference or a milestone reference. **Issue inputs**: `71`, `#71`, or issue URL - resolve directly to the issue number. **Milestone inputs**: `M3`, `M#3`, milestone URL, or `"Milestone Name"` - list open issues in the milestone and select the first unblocked one (an issue is blocked if its Dependencies section references open issues). If multiple unblocked issues exist, pick the one with lowest number. Report to the user which issue was selected and why (e.g., "Selected issue #N — lowest-numbered unblocked issue in milestone M3"). If no unblocked issues exist, report which issues are blocked and stop. ### Handling `needs-triage` Issues If the selected issue has a `needs-triage` label, the issue needs classification before implementation. Read CLAUDE.md and check its `## Label Vocabulary` section for the routing options available. If your project's extension file defines a triage workflow, invoke it now. Otherwise, ask the user whether to proceed directly or reclassify the issue. ### Handling Blocking Labels After resolving the issue and reading it with `gh issue view`, check for blocking labels before proceeding. The label `needs-design` is universally recognized: if an issue carries it, stop immediatel