create-from-context

# Create From Context

Create PARA-compliant resource or meeting notes from information gathered during the current conversation. This is the **inline companion to triage** -- use it when you already have rich context (e.g., from reading meeting notes, pulling Jira tickets, researching a topic) and want to capture it as a vault note without going through the inbox pipeline.

## When to Use This Skill

- Data has been gathered during conversation (web scrapes, API responses, file reads)
- User wants to capture conversation output as a vault note
- Creating a resource or meeting note without an inbox source file

## When NOT to Use This Skill

- Creating a **project** -- use `/para-obsidian:create-project`
- Creating an **area** -- use `/para-obsidian:create-area`
- Processing **inbox items** -- use `/para-obsidian:triage`

## Critical Rules

1. **ALWAYS load vault context first** (Phase 0) -- never suggest areas/projects that don't exist
2. **One question at a time** -- ADHD-friendly, no walls of questions
3. **Pre-fill from context** -- suggest values from conversation, ask "Good?" not "What is X?"
4. **Classification, not invention** -- AI classifies into existing categories; user provides facts
5. **Confirm before creating** -- always show full proposal for approval
6. **DRY references** -- load classification/formatting rules from `@` paths, never duplicate

## Workflow Overview

```
Phase 0: Load Vault Context (ALWAYS FIRST)
    |
Phase 1: Classify Note Type
    |-- Has arguments? -> pre-fill title + infer type
    |-- No arguments? -> ask what to capture
    |-- Apply decision tree -> resource or meeting
    |
Phase 2: Gather Details (template-specific)
    |-- Resource: title, source_format, URL, resource_type, area, summary
    |-- Meeting: title, meeting_type, date, attendees, area/project, summary
    |
Phase 3: Gather Content
    |-- Resource: Layer 1 content from conversation
    |-- Meeting: notes, decisions, action items, follow-up
    |
Phase 4: Presen