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 `gh-issue-resolver` for those steps (or `gh-batch-runner` when several Issues ship together). Several Issues may be planned in one pass. The agreed-plan granularity never changes: **one comment per Issue**, so every downstream skill keeps reading exactly one plan per Issue. See *Step 7*. ## 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 ``` When several Issue numbers were given, run this once per Issue and keep the results side by side — the investigation in Step 3 is shared, the plans in Step 4 are not. 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 `gh-issue-drafter` and its scope is author-approved. Treat its sections as binding input