Turns a GitHub issue number into a full technical specification with problem statement, implementation plan, test scenarios, and file change lists. It checks if you've already fetched the issue, grabs it from GitHub if needed, then walks through your codebase to understand context before writing the spec. Saves everything to a standardized markdown file in your specs folder following a strict naming convention. The template enforces TDD principles and a 300 line file limit, which tells you this is aimed at teams who want structured planning before touching code. Useful if you're tired of issues turning into sprawling PRs because nobody documented what they were actually supposed to build.

skills.sh installs
1.2K
GitHub stars
1.8K
last updated
Aug 21, 2026

Install

$ npx -y skills add neolabhq/context-engineering-kit --skill analyze-issue --agent claude-code

Installs into .claude/skills of the current project.

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.md to 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]

Sponsors

Details

Repository
github.com/neolabhq/context-engineering-kit
Category
Git & Pull Requests
First seen
Jun 3, 2026

More from neolabhq/context-engineering-kit

All 63
1jnmetacode avatarchinese-commit-conventionsjnmetacode/superpowers-zh中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用,不要根据上下1Kskills.sh installs
2dimillian avatargithubdimillian/skillsInteract with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks 891skills.sh installs
3getsentry avatarcreate-prgetsentry/skillsAlias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workf623skills.sh installs
4alirezarezvani avatargit-worktree-manageralirezarezvani/claude-skillsRun parallel feature work safely with Git worktrees. Standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like594skills.sh installs
5intellectronica avatarhere-be-gitintellectronica/agent-skillsInitialise a git repository with optional agent commit instructions and .gitignore. Use when users say "here be git", "init git", "initialise git", or otherwise531skills.sh installs
6parcadei avatargit-commitsparcadei/continuous-claude-v3Git Commit Rules523skills.sh installs