issue-planning-workflow

# GitHub Issue Planning Workflow Skill

This skill provides a comprehensive methodology for planning implementation of GitHub issues.

## Planning Phases

### Phase 1: Issue Intelligence

**Gather all information:**
```bash
# Get issue details
gh issue view {number} --json title,body,labels,milestone,comments,assignees

# Get comments
gh issue view {number} --comments

# Check related PRs
gh pr list --search "#{number}" --json number,title,state
```

**Extract:**
- Core problem/goal
- Acceptance criteria
- Technical hints in description
- Context from comments
- Related issues referenced

### Phase 2: Codebase Exploration

**Systematic exploration:**

1. **Find relevant files:**
```bash
# Search for keywords
rg "keyword" --type ts -l

# Find component files
ls src/components/ | grep -i "feature"
```

2. **Understand current state:**
- Read main files involved
- Note patterns and conventions
- Identify extension points
- Check test coverage

3. **Document findings:**
- File paths with line numbers
- Current implementation details
- Patterns to follow
- Potential challenges

### Phase 3: Clarification

**Ask targeted questions:**

Format:
```markdown
### Question: [Topic]

**Context**: [What you discovered]

**Options**:
A) **[Option]** - [Description]
   - Pros: [Benefits]
   - Cons: [Drawbacks]

B) **[Option]** - [Description]
   - Pros: [Benefits]
   - Cons: [Drawbacks]

**Recommendation**: Option [X] because [reasoning]
```

**Good questions:**
- Technical approach decisions
- Scope clarifications
- Priority of edge cases
- UI/UX preferences

**Avoid:**
- Questions answered in issue
- Questions answerable from code
- Yes/no questions without context

### Phase 4: Plan Generation

**Structure:**

```markdown
## Implementation Plan: #{number}

### Overview
[1-2 sentence summary of approach]

### Architecture Changes
[New components, files, APIs]

### Implementation Steps

#### Step 1: [Title] (Complexity: Low/Medium/High)
**What**: [Description]
**Files**:
- `path/t