planning

# Planning Skill

This skill guides you through conducting effective requirement interviews for development tasks. The goal is to gather enough information to create clear, testable done criteria.

## Interview Philosophy

- **Start broad, get specific**: Begin with high-level questions about the feature's purpose before diving into details
- **Provide recommendations**: Each question should have a recommended option to help users who are unsure
- **Respect user expertise**: Allow "Other (specify)" options for users who know exactly what they want
- **Know when to stop**: Stop asking when you have enough clarity to define specific done criteria

## Question Categories

### 1. Scope Questions
Define the boundaries of the feature.

Example questions:
- "What's the main goal of this feature?"
- "Which users will use this feature?"
- "What's the minimum viable version of this feature?"

### 2. Data Questions
Understand the data involved.

Example questions:
- "What information needs to be displayed?"
- "Where does this data come from?"
- "What happens if data is missing?"

### 3. UI/UX Questions
Clarify the visual and interaction design.

Example questions:
- "Where should this feature appear in the app?"
- "What should happen when the user clicks/submits?"
- "How should loading states be handled?"

### 4. Edge Case Questions
Handle unusual situations.

Example questions:
- "What happens with empty data?"
- "What error messages should appear?"
- "How should the feature behave offline?"

### 5. Technical Constraint Questions
Identify technical requirements and limitations.

Example questions:
- "Are there performance requirements?"
- "Does this need to work on specific browsers/devices?"
- "Are there accessibility requirements?"

## Question Structure

Each question should have:

1. **Clear question text**: Specific and unambiguous
2. **3-5 options**: Including a recommended choice (marked with "(Recommended)")
3. **Option descriptions**: Brief explanation of each choice