Inbox

Present items in batches (3-5 at a time), not all at once. Let the user decide before moving to the next batch.

4. Execute Decisions

For each decision:

• Read the relevant template before creating any new note
• Follow naming conventions from ${PROGRESSIVE_VAULT_STRUCTURE}
• Use [[wikilinks]] to connect new notes to existing vault content
• If creating an event note, check if it belongs to an existing trip

5. Summary

After processing, report:

Processed: X items
  → Moved to [locations]: N items
  → Created new notes: N items
  → Discarded: N items
  → Remaining in Inbox: N items

Principles

• Batch processing — don't overwhelm with all items at once
• User decides — suggest routing, don't auto-route
• Connect to context — if an item relates to an active project, say so
• Templates first — always read template before creating structured notes
• Stale is OK — not everything captured needs to become a note. Discarding is a valid outcome.

Integration

• progressive-context: For vault structure and active project awareness
• daily: Run /daily first to see today's context, then /inbox to process
• trip-planning: If inbox items are trip-related, suggest using trip-planning skill instead