plan-generation

# Plan Generation

Guide for generating high-quality plans from meta-prompt templates.

## When to Use

- Generating plans from `/chore`, `/bug`, `/feature` templates
- Reviewing generated plans for completeness
- Ensuring plans follow team standards
- Improving plan quality and specificity

## Plan Generation Process

### Step 1: Understand the Request

Parse the high-level description:

```text
Input: "Add user authentication with OAuth"

Extract:
- Domain: Authentication
- Scope: User-facing, OAuth protocol
- Complexity: Medium-high (external integration)
```

### Step 2: Activate Reasoning

Use extended thinking for complex planning:

```markdown
THINK HARD about:
- What files need to change?
- What are the dependencies?
- What could go wrong?
- How will we verify success?
```

### Step 3: Explore the Codebase

Gather context before planning:

- Read README for project structure
- Identify relevant existing patterns
- Find test examples to follow
- Locate configuration files

### Step 4: Fill the Template

Complete every section with specifics:

```markdown
## Relevant Files
- src/auth/OAuthProvider.ts (create)
- src/auth/index.ts (modify - add export)
- src/config/oauth.ts (create)
- tests/auth/oauth.test.ts (create)
```

### Step 5: Validate Plan Quality

Check against quality criteria before finalizing.

## Quality Criteria

Every plan should meet these standards:

### Specificity

**Bad**: "Update the component"
**Good**: "Update UserProfile.tsx to add loading state on line 45"

### Actionability

**Bad**: "Handle errors appropriately"
**Good**: "Add try/catch in fetchUser(), log errors with console.error, show ErrorBoundary"

### Completeness

All template sections filled:

- [ ] Description explains what and why
- [ ] Relevant Files lists all files to touch
- [ ] Tasks are numbered and specific
- [ ] Validation Commands are executable
- [ ] Notes capture edge cases

### Testability

Every plan must include validation:

```markdown
## Validation Commands

-