git:analyze-issue
Please analyze GitHub issue #$ARGUMENTS and create a technical specification.
Follow these steps:
-
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)
- Look for the issue file in
-
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
- Read
-
Understand the requirements thoroughly
-
Review related code and project structure
-
Create a technical specification with the format below
Technical Specification for Issue #$ARGUMENTS
More from neolabhq/context-engineering-kit
sdd:plan
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task
550sdd:implement
Implement a task with automated LLM-as-Judge verification for critical steps
525customaize-agent:prompt-engineering
Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.
512code-review:review-local-changes
Comprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
511sdd:brainstorm
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
509sdd:add-task
creates draft task file in .specs/tasks/draft/ with original user intent
503