Issue
Fetch a GitHub issue, explore the codebase, ask clarifying questions, and produce an implementation plan. Stops before building — hand off to /dev when ready. Use when planning implementation from a GitHub issue.From its SKILL.md
npx -y skills add mike-diff/ai-coding-configs --skill issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 373 tokens by cl100k_base, as published. Nobody here has run it
/issue — GitHub Issue Analysis & Planning
Analyse a GitHub issue, explore the codebase, clarify ambiguities, and produce a detailed implementation plan. Stops before implementation — hand off to /dev when ready.
<issue_input> $ARGUMENTS </issue_input>
Phases
| # | Phase | What happens |
|---|---|---|
| 1 | Fetch | Parse input (number or URL), fetch issue via gh issue view |
| 2 | Detect | Identify tech stack from manifest files |
| 3 | Explore | Delegate to the built-in Explore subagent, get affected files and patterns |
| 4 | Clarify | Present understanding, ask questions — STOP for user input |
| 5 | Plan | Create implementation plan with AI risk assessment |
| 6 | Todo | Generate task list via TodoWrite, then STOP |
Key Constraints
- MUST fetch the issue using
ghCLI - Delegate wide codebase exploration to the built-in Explore subagent; explore directly only when the area is already known
- MUST stop after creating the todo list — do NOT implement
- Use sequential-thinking MCP for complex planning decisions
- Use context7 MCP for library documentation lookups
Handoff
When complete:
/dev "Implement #[issue-number]" @[plan file if saved]
Full Workflow
For complete phase-by-phase instructions, gh commands, exploration prompts, plan format, and AI assessment template, see references/workflow.md.
What ships with it: 1 file
10.1 KB alongside SKILL.md
references/
- workflow.md10.1 KB
Gives 0 of the 12 instructions most plan spec skills give in 373 tokens
Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07
- Ask one question at a timein 51 of 1099
- Break plans into vertical slicesin 29 of 1099, across 11 files
- Publish issues in dependency orderin 27 of 1099, across 9 files
- Iterate until user approves the breakdownin 25 of 1099, across 7 files
- Explore the repository to understand the codebase statein 24 of 1099, across 7 files
- Use domain glossary vocabularyin 23 of 1099, across 5 files
- Apply correct triage labels to published issuesin 23 of 1099, across 5 files
- Prefer AFK slices over HITLin 22 of 1099, across 7 files
- Write a specification before writing any codein 22 of 1099, across 14 files
- Write failing tests before implementation codein 22 of 1099, across 20 files
- Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
- Respect existing architecture decision recordsin 20 of 1099, across 5 files
Said here and by no other author read
- explore directly only when the area is known
- use sequential-thinking mcp for complex planning
- use context7 mcp for library documentation
- stop after creating the todo list
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.