plan

# Plan Skill

Structured planning through interview and draft management.

## When This Skill Activates

| Category | Trigger Phrases |
|----------|-----------------|
| **Start planning** | `/plan <topic>`, `let's plan`, `plan for`, `help me plan` |
| **Continue draft** | `continue planning`, `back to plan`, `resume plan` |
| **Finalize** | `make it a plan`, `finalize plan`, `generate plan`, `create the plan` |
| **Abandon** | `cancel plan`, `abandon planning`, `forget the plan` |

## Planning Workflow

### Phase 1: Initiation

When triggered with a topic:

1. Create draft file at `.claude/plans/drafts/{topic-slug}.md`
2. Initialize with template structure
3. Begin interview

**Draft location:** `.claude/plans/drafts/{topic-slug}.md`
**Final plan location:** `.claude/plans/{topic-slug}.md`

### Phase 2: Interview

Ask focused questions to gather requirements. Keep it to 3-5 core questions:

**Core Questions:**
1. "What problem does this solve?" (understand context)
2. "What's the scope - minimal viable vs complete?" (set boundaries)
3. "Any constraints, non-goals, or things to avoid?" (define exclusions)

**Follow-up Questions (as needed):**
- Technical approach preferences
- Dependencies on other work
- Priority/timeline considerations

After each answer, update the draft file with new information.

Use `AskUserQuestion` tool for structured multi-choice questions when options are clear.

### Phase 3: Research

Before finalizing, research the codebase:

```
Agent: oh-my-claude:scout
Task: Find relevant files for {topic}
Why: Need to understand existing code before planning changes
Expected: List of files that will be affected
```

```
Agent: oh-my-claude:librarian
Task: Read and summarize key files
Why: Need context for implementation planning
Expected: Summary of current implementation patterns
```

Add findings to draft under "## Research Findings".

### Phase 4: Confirmation

When user says "make it a plan" or similar:
1. Review draft completeness
2. Transform dr