create-project

# Create Project

Create PARA-compliant project notes with validated area connections through collaborative dialogue.

## Core Philosophy

**From Tiago Forte's PARA Method:**

- **Project** = Has a specific outcome AND deadline. Can be marked "complete."
- **Area** = Standard to maintain. Continuous, no end date.
- **Every project falls within an area** - they're interdependent.
- **Organize by actionability**, not subject matter.

This skill ensures projects are well-defined and properly connected to your life structure.

## Critical Rules

1. **ALWAYS load areas first** - Never suggest areas that don't exist in the vault
2. **NEVER invent connections** - Only offer areas from the loaded list or create new ones
3. **Projects MUST have outcomes** - If no clear outcome, it might be an area instead
4. **Projects MUST have deadlines** - "Ongoing" means it's an area, not a project
5. **Area selection is REQUIRED** - Every project falls within an area
6. **Classification, not invention** - AI classifies into existing categories; user provides facts

## Workflow Overview

```
Phase 0: Load Vault Context (ALWAYS FIRST)
    ↓
Phase 1: Gather Project Intent
    ├── What outcome?
    └── When complete? (validates it's a project)
    ↓
Phase 2: Area Selection (CRITICAL - prevents invalid areas)
    ├── Present numbered list from vault
    ├── User selects OR creates new
    └── NEVER accept free-text area names
    ↓
Phase 3: Confirm & Create
    ├── Present complete proposal
    ├── User approves or adjusts
    └── Create with validated frontmatter
```

---

## Phase 0: Load Vault Context

**ALWAYS fetch vault context before doing anything else:**

```
para_list_areas({ response_format: "json" })
para_list_projects({ response_format: "json" })
```

Store these lists for:
- Area validation in Phase 2
- Detecting duplicate project names
- Understanding user's current structure

**If user provides context in initial message**, still load areas first before responding.

---

## P