analysis-iterative

# Iterative Analysis

## Overview

Guide deep thinking through progressive, one-at-a-time questioning. Each question builds on previous answers, creating a collaborative exploration that concludes with a structured synthesis document.

## When to Use

- Brainstorming sessions that need structured exploration
- Deep analysis of complex problems with multiple decision points
- Thinking through feature requirements before specification
- Enriching sparse feature descriptions for `/humaninloop:specify`
- Exploring trade-offs that require deliberate choices
- When users need help organizing their thinking on a topic

## When NOT to Use

- **Quick clarifications** - Simple questions don't need iterative questioning
- **Implementation details** - Use planning skills instead
- **Specification review** - Use `humaninloop:analysis-specifications` instead
- **When user has clear direction** - Don't slow down decisive users
- **Time-sensitive decisions** - Iterative questioning takes time

## Workflow Phases

### Phase 1: Opening

When triggered, acknowledge the topic and set expectations:

```
I'll help you think through [topic] with a series of focused questions.

For each question, I'll present options with my recommendation. Feel free to
disagree—I'll push back to help strengthen your thinking.

Let's begin.
```

Then ask the first question.

### Phase 2: Iterative Questioning

**Core Rules:**
1. ONE question per turn—never multiple questions
2. Always provide 2-3 concrete options
3. Always state your recommendation with reasoning
4. After each answer, briefly show how it affects the analysis before the next question

**Question Format:**

```
[Brief context showing current understanding and how previous answer shaped thinking]

**Question [N]**: [Clear, focused question]

**Options:**
- **A) [Option name]**: [What this means and its implications]
- **B) [Option name]**: [What this means and its implications]
- **C) [Option name]**: [What this means and its implications]

*