Create PARA notes (resource or meeting) from data gathered during conversation. Interactive workflow that classifies, proposes, and creates with content injection. Use when structured information exists in conversation context and needs capturing as a vault note.
Create PARA notes (resource or meeting) from data gathered during conversation. Interactive workflow that classifies, proposes, and creates with content injection. Use when structured information exists in conversation context and needs capturing as a vault note.
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
ALWAYS load vault context first (Phase 0) -- never suggest areas/projects that don't exist
One question at a time -- ADHD-friendly, no walls of questions
Pre-fill from context -- suggest values from conversation, ask "Good?" not "What is X?"
Classification, not invention -- AI classifies into existing categories; user provides facts
Confirm before creating -- always show full proposal for approval
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: Present Proposal & Confirm
|
Phase 5: Execute (create + inject + commit)
|
Phase 6: Report & Next Steps
Phase 0: Load Vault Context
ALWAYS fetch vault context before doing anything else:
Even if the user provides context in $ARGUMENTS, load vault context first.
Phase 1: Classify Note Type
If $ARGUMENTS provided
Pre-fill the title from $ARGUMENTS and infer the template type:
You mentioned: "$ARGUMENTS"
Based on the conversation context, I suggest creating a **[resource/meeting]** note.
Does that sound right? (resource / meeting / something else)
If no arguments
Ask what to capture:
What information from this conversation would you like to capture as a vault note?
I can create:
1. **Resource** -- knowledge to learn from (article, video, idea, reference)
2. **Meeting** -- notes from a discussion (attendees, decisions, action items)
Created: [emoji] [Title].md -> [destination folder]
Linked to: [[Area Name]]
[For resources: Layer 1 content injected ([word count] words)]
[For meetings: Sections populated: Notes, Decisions, Action Items, Follow-up]
Committed to vault.
Would you like to:
1. **Create another note** from this conversation
2. **Distill** the resource (extract key insights)
3. **Done** - note is ready
Error Handling
Error
Recovery
para_create fails
Show error, preserve all gathered data, offer retry
para_replace_section fails
Note exists without Layer 1 -- inform user, they can add content manually
para_commit fails (dirty tree)
Inform user, suggest committing existing changes first
No areas exist
Offer to create one first (same pattern as create-project Phase 2.3)
User cancels
Graceful exit, no cleanup needed
Example Interactions
Resource from Web Research
User: [earlier in conversation, scraped an article about TypeScript generics]
User: /para-obsidian:create-from-context TypeScript generics guide
AI: Loading vault context...
Based on the article we just read, I suggest creating a **resource** note.
**Title:** "TypeScript Generics - A Practical Guide"
**Source format:** article (📰)
Does that look right? (yes / adjust)
User: yes
AI: Which area does this belong to?
1. 🤖 AI Practice
2. 💼 Career
3. 📝 Note Taking
User: 2
AI: [presents full proposal with Layer 1 content preview]
User: yes
AI: Created: 📰 TypeScript Generics - A Practical Guide.md -> 03 Resources
Linked to: [[💼 Career]]
Layer 1 content injected (1,240 words)
Committed to vault.
Meeting from Discussion
User: [earlier, discussed sprint retro with notes about what went well/badly]
User: /para-obsidian:create-from-context
AI: What information from this conversation would you like to capture?
1. **Resource** -- knowledge to learn from
2. **Meeting** -- notes from a discussion
User: 2
AI: I suggest:
**Title:** "Sprint 42 Retrospective"
**Meeting type:** retro
Good? (yes / adjust)
User: yes
AI: When did this meeting happen?
User: today at 2pm
AI: [extracts attendees, presents sections for confirmation]
User: yes
AI: [presents full proposal]
User: yes
AI: Created: Sprint 42 Retrospective.md -> 04 Archives/Meetings
Sections populated: Notes, Decisions Made, Action Items, Follow-up
Committed to vault.
