$npx -y skills add NeoLabHQ/context-engineering-kit --skill analyze-issueAnalyze a GitHub issue and create a detailed technical specification
| 1 | Please analyze GitHub issue #$ARGUMENTS and create a technical specification. |
| 2 | |
| 3 | Follow these steps: |
| 4 | |
| 5 | 1. Check if the issue is already loaded: |
| 6 | - Look for the issue file in `./specs/issues/` folder |
| 7 | - File naming pattern: `<number-padded-to-3-digits>-<kebab-case-title>.md` |
| 8 | - If not found, fetch the issue details from GitHub (see step 2) |
| 9 | |
| 10 | 2. Fetch the issue details (if not already loaded): |
| 11 | - Read `.claude/commands/load-issues.md` to understand how to fetch issue details |
| 12 | - Save the issue file following the load-issues.md format |
| 13 | |
| 14 | 3. Understand the requirements thoroughly |
| 15 | 4. Review related code and project structure |
| 16 | 5. Create a technical specification with the format below |
| 17 | |
| 18 | # Technical Specification for Issue #$ARGUMENTS |
| 19 | |
| 20 | ## Issue Summary |
| 21 | - Title: [Issue title from GitHub] |
| 22 | - Description: [Brief description from issue] |
| 23 | - Labels: [Labels from issue] |
| 24 | - Priority: [High/Medium/Low based on issue content] |
| 25 | |
| 26 | ## Problem Statement |
| 27 | [1-2 paragraphs explaining the problem] |
| 28 | |
| 29 | ## Technical Approach |
| 30 | [Detailed technical approach] |
| 31 | |
| 32 | ## Implementation Plan |
| 33 | 1. [Step 1] |
| 34 | 2. [Step 2] |
| 35 | 3. [Step 3] |
| 36 | |
| 37 | ## Test Plan |
| 38 | 1. Unit Tests: |
| 39 | - [test scenario] |
| 40 | 2. Component Tests: |
| 41 | - [test scenario] |
| 42 | 3. Integration Tests: |
| 43 | - [test scenario] |
| 44 | |
| 45 | ## Files to Modify |
| 46 | - [file path]: [changes] |
| 47 | |
| 48 | ## Files to Create |
| 49 | - [file path]: [purpose] |
| 50 | |
| 51 | ## Existing Utilities to Leverage |
| 52 | - [utility name/path]: [purpose] |
| 53 | |
| 54 | ## Success Criteria |
| 55 | - [ ] [criterion 1] |
| 56 | - [ ] [criterion 2] |
| 57 | |
| 58 | ## Out of Scope |
| 59 | - [item 1] |
| 60 | - [item 2] |
| 61 | |
| 62 | Remember to follow our strict TDD principles, KISS approach, and 300-line file limit. |
| 63 | |
| 64 | IMPORTANT: After completing your analysis, SAVE the full technical specification to: |
| 65 | `./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md` |
| 66 | |
| 67 | For example, for issue #7 with title "Make code review trigger on any *.SQL and .sh file changes", save to: |
| 68 | `./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md` |
| 69 | |
| 70 | After saving, provide a brief summary to the user confirming: |
| 71 | - Issue number and title analyzed |
| 72 | - File path where the specification was saved |
| 73 | - Key highlights from the specification (2-3 bullet points) |