yds-gh-issue-plannerlisted

# GitHub Issue Planner ## Overview Fetch a GitHub Issue, analyze its content, investigate related code in the repository, and present a structured response plan to the user. After the user confirms, post the agreed plan as a comment on the issue. Implementation and PR creation are out of scope — use `yds-gh-issue-resolver` for those steps. ## Workflow ### Step 1: Fetch the Issue Run the following command (replace `<id>` with the issue number): ```bash gh issue view <id> --json number,title,body,labels,assignees,state,url,comments ``` If no repository context is clear, also run: ```bash gh repo view --json nameWithOwner ``` Extract from the response: - **Title** and **body**: the core problem statement - **Labels**: bug / feature / enhancement / etc. — determines response approach - **Comments**: additional context, workarounds, or constraints from stakeholders **Pre-scoped Issues:** if the body contains `<!-- gh-issue-drafter:scoped-issue -->`, the Issue was drafted via `yds-gh-issue-drafter` and its scope is author-approved. Treat its sections as binding input to the plan: - **完了条件 (Done)** — the contract the plan must satisfy; every condition must be covered by an implementation step or a test in the plan - **触らない範囲 (Out of scope)** — hard boundaries; reject any plan direction that crosses them - **設計方針 (Design constraints)** — constraints on how, not just what Do not re-ask the user about scope that these sections already answer — raise open questions only f