inbox

/inbox — Quick Capture & Process

Dual-mode command for fast capture and later processing.

Context

Today's date: !date +%Y-%m-%d Inbox contents: !ls 00-inbox/*.md 2>/dev/null

Reference template: @_templates/inbox.md Config: @_core/config.yaml Processing logic: @_core/PROCESSING.md

Input

User input: $ARGUMENTS

Mode Detection

• Capture mode: If $ARGUMENTS has content
• Process mode: If $ARGUMENTS is empty

---

Capture Mode (with content)

1. Auto-detect

   • Project: Look for project names from config
   • Type: daily, decision, blocker, meeting, doc

2. Create Inbox Note

   • Filename: 00-inbox/{date}-{slug}.md
   • Tag with detected project/type
   • Status: unprocessed

3. Append to Vault Log

   • Append entry to 01-index/_vault-log.md (see .claude/rules/vault-log.md)
   • Action: inbox-capture
   • Details: what was captured and detected type

4. Output

   Captured to: 00-inbox/{filename}
   Detected: {project} / {type}
   Process later with: /inbox
   

---

Process Mode (no content)

Use session tasks for batch visibility:

TaskCreate: "Scan and classify inbox items"
  activeForm: "Scanning inbox..."

TaskCreate: "Route items to destinations"
  activeForm: "Routing inbox items..."

1. Scan Inbox

   • List all .md files in 00-inbox/
   • Read and classify each

2. Present Plan

   ## Processing Plan
   
   | # | Content Preview | Type | Project | Action |
   |---|-----------------|------|---------|--------|
   | 1 | "Shipped login..." | daily | project-a | Update daily |
   | 2 | "Blocked on API..." | blocker | project-a | Create blocker |
   
   Proceed? (y/n/edit)
   

3. Route Items

   • For each confirmed item:
     • Route to appropriate handler (/daily, /block, /decide, etc.)
   • Mark processed inbox files

4. Append to Vault Log

   • Append one inbox-route entry per batch to 01-index/_vault-log.md (see .claude/rules/vault-log.md)
   • Details: count of items routed and their types