plan-generator

## Purpose

Given code exploration results, generate a comprehensive plan that:
- Explains root cause clearly
- Specifies exact changes needed
- Sets scope boundaries (what we won't do)
- Provides testing approach
- Looks professional in GitHub comments

## Usage

Include this file when generating plans:

```
Use lib/plan-generator to create fix plan from exploration results
```

## Template Structure

```markdown
## 🤖 Automated Fix Plan for Issue #<NUMBER>

**Summary:** [One clear sentence: what's broken and how we'll fix it]

**Estimated scope:** X files changed, Y tests added/modified

**Confidence:** [High/Medium/Low based on exploration clarity]

<details>
<summary>📋 Detailed Plan</summary>

### 🔍 Root Cause Analysis
[Technical explanation of what's causing the issue]

### ✅ What We'll Do
- [ ] Change 1 (`file.ts:line`)
- [ ] Change 2 (`file.ts:line`)
- [ ] Add test for scenario X

### ❌ What We Won't Do
- Explanation of what's out of scope and why

### 📝 Files to Change
- `path/to/file1.ts` - Description of change
- `path/to/file2.ts` - Description of change
- `tests/file.test.ts` - Add test for X

### ✅ Testing Approach
- Unit test strategy
- Integration test needs
- Manual verification steps

### ⚠️ Risks & Considerations
[Things to watch during implementation]

</details>

---
**Next Steps:**
- 👍 React with thumbs up if this plan looks good
- 💬 Comment "approve" or "lgtm" to proceed
- ✏️ Comment with feedback if changes needed

Once approved, run: `/continue-issue <NUMBER>`
```

## Input Format

Expects exploration results:

```typescript
interface ExplorationResults {
  rootCause: string;           // What's causing the issue
  relevantFiles: FileInfo[];   // Files to modify
  confidence: 'High' | 'Medium' | 'Low';
  understanding: string;        // How the code works
}

interface FileInfo {
  path: string;                // e.g., "src/auth/config.ts"
  lines?: string;              // e.g., "12-15"
  reason: string;              // Why this file matt