Creating Wizards

Meta-skill for AskUserQuestion wizard flows with anti-patterns and bidirectional pattern.

Core Principle

AskUserQuestion is key - every question should:

1. Teach - User learns something about capabilities
2. Collect - Claude learns user preferences

Anti-Patterns (NEVER DO)

Bidirectional Pattern

Question: "[Tool] can do X. Would you like Y?"
Header: "Feature"
Options:
- "Enable X" - Description of what happens
- "Skip" - I'll set this up later

Teaching: User learns X exists
Collecting: preference_for_x

Question Design Checklist

• Header <= 12 characters
• 2-4 concrete options
• Each option has description
• Teaching moment included
• Data field documented
• No "Other" mention

Wizard Structure Template

### Step N: {Purpose}

Question: "{Question text ending with ?}"
Header: "{<=12 chars}"
Options:
- "{Option 1}" - {Description}
- "{Option 2}" - {Description}

Teaching: User learns {capability}
Collecting: {field_name}

**Processing:**
- If Option 1: {action}
- If Option 2: {action}

Progressive Disclosure

• Keep each step focused on ONE decision
• Total wizard experience < 5 minutes
• Use checkpoints every 3-4 steps
• Allow "Go back" on confirmation step

Validation Rules

Machine-Verifiable

Human Review

• Teaching moment clear?
• Options mutually exclusive?
• Flow makes sense?