# analyze-issue

Analyze a GitHub issue and create a detailed technical specification.

* Purpose - Transform issues into actionable development tasks
* Output - Technical specification with requirements

```bash
/git:analyze-issue <issue-number>
```

## Arguments

Issue number (e.g., 42) - required.

## How It Works

1. **Issue Fetching**: Retrieves issue details from GitHub
2. **Requirements Extraction**: Identifies user stories and acceptance criteria
3. **Technical Analysis**: Determines APIs, data models, and dependencies
4. **Task Breakdown**: Creates actionable subtasks
5. **Complexity Assessment**: Estimates implementation effort

## Usage Examples

```bash
# Analyze issue before starting work
> /git:analyze-issue 123

# Use with SDD workflow
> /git:analyze-issue 123
> /sdd:01-specify

# Plan sprint work
> /git:load-issues
> /git:analyze-issue 45
> /git:analyze-issue 67
```

## Best Practices

* Analyze before coding - Understand requirements first
* Check issue completeness - Request clarification if needed
* Note dependencies - Identify related issues or PRs
* Use for planning - Helps estimate and prioritize work


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cek.neolab.finance/plugins/git/analyze-issue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.