| name | plan-github-issue |
| description | Analyze a GitHub issue and write an implementation plan into the issue itself — without implementing anything. Use this skill whenever the user invokes "/plan-github-issue", says "plan issue |
| version | 1.0.0 |
plan-github-issue
Analyze and plan a solution for the GitHub issue given as the skill argument (issue number or URL). Use the GitHub CLI (gh) for all GitHub-related tasks.
Steps
- Get the issue details:
gh issue view <n> (add --comments — discussion often contains constraints the description lacks)
- Understand the problem described in the issue
- Search the codebase for relevant files; read enough to ground the plan in the actual code
- Design a plan for the necessary changes: affected files, approach, risks, test strategy
- Do not implement the fix — this skill ends at the plan
- Update the issue description with the plan (
gh issue edit), appending under a clearly marked plan section rather than overwriting the reporter's text
- Label the issue:
gh label list to see available labels; apply relevant ones- Create new labels with
gh label create only if genuinely necessary
Editing the issue publishes the plan — keep it professional and grounded; if anything about the issue is ambiguous, note open questions in the plan section instead of guessing silently.
