---
name: plan
description: Strategic planning with interview workflow for complex tasks
---

# Plan Skill

Create comprehensive implementation plans through structured analysis.

## When to Use

- Before starting a complex task
- When requirements are unclear
- When multiple approaches are possible
- For tasks affecting multiple files/systems

## Planning Modes

### Interview Mode (for unclear requirements)

When the request is vague or broad:
1. Ask clarifying questions
2. Understand constraints and goals
3. Create detailed plan

**Triggers for interview mode:**
- Vague verbs: "improve", "enhance", "fix"
- No specific files mentioned
- Multiple possible approaches

### Direct Mode (for clear requirements)

When the request is detailed:
1. Analyze requirements briefly
2. Create plan immediately

**Triggers for direct mode:**
- Specific files/functions mentioned
- Clear acceptance criteria
- User says "skip interview"

## Interview Questions

When interviewing, ask about:

1. **Goals**: What's the end state?
2. **Constraints**: Time, tech stack, compatibility
3. **Context**: Why is this needed now?
4. **Risks**: What could go wrong?
5. **Preferences**: Any specific approaches?

**Rule**: Ask ONE question at a time. Wait for response.

## Plan Output Format

```markdown
# Implementation Plan: [Feature Name]

## Overview
Brief summary of what this plan accomplishes.

## Prerequisites
- Required setup or decisions
- Dependencies

## Tasks

### Phase 1: [Name]

#### Task 1.1: [Task Name]
**Description:** What needs to be done
**Files:** Files to create/modify
**Verification:** How to verify completion
**Complexity:** Low/Medium/High

### Phase 2: [Name]
...

## Risks & Mitigations

| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk] | Low/Med/High | Low/Med/High | [Solution] |

## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] All tests pass
```

## Quality Checklist

Before finalizing a plan:
- [ ] All tasks are atomic and independently completable
- [ ] Dependencies between tasks are explicit
- [ ] Each task has verification criteria
- [ ] Risks are identified with mitigations
- [ ] Success criteria are testable
