Analyze Issue
- 901 installs
- 1.3k repo stars
- Updated August 3, 2026
- neolabhq/context-engineering-kit
analyze-issue is a Claude Code skill that transforms a GitHub issue number into a complete technical specification with implementation steps, test plan, and file changes for developers who need actionable specs from trac
About
analyze-issue is a skill from neolabhq/context-engineering-kit that accepts a GitHub issue number as an argument and produces a detailed technical specification. The workflow checks ./specs/issues/ for an existing file matching the pattern number-padded-to-3-digits-kebab-case-title.md, fetches missing issues via gh issue commands following load-issues.md instructions, then writes a spec covering implementation steps, a test plan, and proposed file changes. Developers reach for analyze-issue when a GitHub ticket is too vague for direct coding and needs structured decomposition before sprint work. Allowed tools include Bash(gh issue:*), Read, Write, Glob, and Grep, making it a git-integrated planning step in context-engineering workflows.
- Automatically loads or fetches GitHub issues using gh CLI
- Analyzes project structure and related code via glob/grep
- Produces a standardized technical specification template
- Generates prioritized implementation plan, test plan, and affected files list
- Saves reusable markdown specs to ./specs/issues/ for downstream agent workflows
Analyze Issue by the numbers
- 901 all-time installs (skills.sh)
- +26 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #538 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/neolabhq/context-engineering-kit --skill analyze-issueAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 901 |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 3, 2026 |
| Repository | neolabhq/context-engineering-kit ↗ |
How do you turn a GitHub issue into a tech spec?
Turn a vague GitHub issue into a complete technical specification with implementation steps, test plan, and file changes.
Who is it for?
Developers using GitHub Issues who want agent-generated technical specifications before starting implementation on a ticket.
Skip if: Teams without GitHub Issues or developers who only need code review on an existing pull request.
When should I use this skill?
A developer provides a GitHub issue number and asks for a technical specification, implementation plan, or test plan.
What you get
Markdown technical specification with implementation steps, test plan, and file-change list under ./specs/issues/.
- Technical specification markdown
- Test plan
- File change list
Files
Please analyze GitHub issue #$ARGUMENTS and create a technical specification.
Follow these steps:
1. Check if the issue is already loaded:
- Look for the issue file in
./specs/issues/folder - File naming pattern:
<number-padded-to-3-digits>-<kebab-case-title>.md - If not found, fetch the issue details from GitHub (see step 2)
2. Fetch the issue details (if not already loaded):
- Read
.claude/commands/load-issues.mdto understand how to fetch issue details - Save the issue file following the load-issues.md format
3. Understand the requirements thoroughly 4. Review related code and project structure 5. Create a technical specification with the format below
Technical Specification for Issue #$ARGUMENTS
Issue Summary
- Title: [Issue title from GitHub]
- Description: [Brief description from issue]
- Labels: [Labels from issue]
- Priority: [High/Medium/Low based on issue content]
Problem Statement
[1-2 paragraphs explaining the problem]
Technical Approach
[Detailed technical approach]
Implementation Plan
1. [Step 1] 2. [Step 2] 3. [Step 3]
Test Plan
1. Unit Tests:
- [test scenario]
2. Component Tests:
- [test scenario]
3. Integration Tests:
- [test scenario]
Files to Modify
- [file path]: [changes]
Files to Create
- [file path]: [purpose]
Existing Utilities to Leverage
- [utility name/path]: [purpose]
Success Criteria
- [ ] [criterion 1]
- [ ] [criterion 2]
Out of Scope
- [item 1]
- [item 2]
Remember to follow our strict TDD principles, KISS approach, and 300-line file limit.
IMPORTANT: After completing your analysis, SAVE the full technical specification to: ./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md
For example, for issue #7 with title "Make code review trigger on any *.SQL and .sh file changes", save to: ./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md
After saving, provide a brief summary to the user confirming:
- Issue number and title analyzed
- File path where the specification was saved
- Key highlights from the specification (2-3 bullet points)
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Choose analyze-issue for GitHub-issue-to-spec conversion; use prd-writer when starting a new product initiative without an existing tracker ticket.
FAQ
Where does analyze-issue save specifications?
analyze-issue saves specifications to the ./specs/issues/ folder using the naming pattern padded-issue-number-kebab-case-title.md. The skill checks that folder first to avoid duplicate GitHub fetches.
What does analyze-issue include in each spec?
analyze-issue produces a technical specification with implementation steps, a test plan, and a list of file changes for the given GitHub issue number. The skill uses gh issue commands when the issue is not already cached locally.
Is Analyze Issue safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.