plan-generator

# Plan Generator Skill

This skill creates standalone plan files for complex projects that enable autonomous, phased execution with real-time progress tracking.

## When to Use This Skill

Use this skill when:
- User asks to create a project plan or PLAN file
- User wants to break down a complex project into phases and steps
- User needs a self-contained planning document for large initiatives

Do NOT use this skill when:
- User wants to EXECUTE an existing plan (use `plan-executor` skill instead)
- User references an existing PLAN file to continue work

## Plan File Naming

Plans are feature/project-specific and can be named flexibly:
- Single feature: `PLAN-{feature}.md` (e.g., `PLAN-auth.md`, `PLAN-api.md`)
- Main project plan: `PLAN.md`
- Multiple plans can coexist in one repository for different features

**Always ask the user what filename they want** or suggest based on the project/feature name.

## Plan File Structure

When creating a plan file, follow this exact structure:

### 1. Instructions for Claude Code (TOP OF FILE)

This section MUST be first. Keep it concise (~15 lines):

```markdown
## Instructions for Claude Code

When working on this plan:
1. **Use the `plan-executor` skill** to execute this plan
2. **Work autonomously** through phases without stopping for approval (unless blocked)
3. **Document findings** in the Notes & Decisions section

**Execution Mode:** [direct|worker]
**Auto-continue:** [yes|no]
**Commit after phase:** [yes|no] (include PLAN file: [yes|no])
```

### 2. Current Phase Indicator

Simple status at the top:
- `**Current Phase:** Phase 1: [Phase Name]`
- `**Current Phase:** COMPLETE`

### 3. Project Overview

- Clear description of the end goal
- Context about what the project achieves
- Key requirements (bulleted list)
- Any constraints or dependencies

### 4. Phase Breakdown

Each phase should include:

```markdown
## Phase N: [Phase Name]

Brief description of what this phase accomplishes.

### Step N.1: [Step title]
Detaile