/triage - Universal Inbox Routing

You are helping the user process their universal inbox. Items can be links, tasks, project updates, new opportunities, or general thoughts. Use intelligent routing to send each item to the right destination.

Behavior

1. Read inbox at 01_Inbox/00_INBOX.md
2. Count items in the Inbox section
3. Ask mode:
   • If user said /triage all → Process all items
   • Otherwise ask: "You have X items in inbox. Process: [number] or 'all'"
4. For each item:
   • Classify type (Link, Task, Project Update, New Opportunity, Thought)
   • Determine destination
   • Calculate confidence (High/Medium/Low)
   • Show routing decision
   • If Medium or Low confidence, ask confirmation
   • Execute routing
   • Archive decision
   • Remove from inbox
5. Output summary of routing decisions

Item Classification

Type 1: Links

Pattern detection:

• Starts with http://, https://, or www.
• Contains .com, .org, .ai, .io, etc.
• Domain-like structure

Destination: 01_Inbox/00_EXPLORE.md → Unprocessed section

Confidence: Always High (clear pattern match)

Action: Append link to end of Unprocessed section

Type 2: Tasks

Pattern detection:

• Has checkbox: - [ ] or [ ]
• Starts with imperative verb: Email, Call, Schedule, Buy, Check, Send, Follow up, Review, Update, Fix, etc.
• Action-oriented language
• Contains deadline indicators: #today, tomorrow, next week

Destination: 01_Inbox/01_TASKS.md → Open section

Confidence:

• High: Has checkbox OR clear imperative verb
• Medium: Action-oriented but ambiguous phrasing

Action:

1. Ensure checkbox format: - [ ] [task text]
2. Preserve any #today or date tags
3. Append to Open section in 01_TASKS.md

Type 3: Project Updates

Pattern detection:

• Mentions project by wikilink: [[Project Name]] or [[Legata Index]]
• Contains project keywords: Legata, HPM, Dossier, "Job Search", etc.
• Discusses progress, meetings, decisions, next steps
• References people associated with projects: Alesia, Bryan, Theron, etc.

Destination: Project file in 02_Projects/

Smart Routing (CRITICAL):

DO NOT use hardcoded keyword matching. Instead:

1. If wikilink present:
   • Extract project from wikilink
   • Confidence: High
   • Destination: Linked file
2. If no wikilink, semantic matching required:
   • Read 02_Projects/Project Index.md to get active projects
   • Use AI to determine best match based on:
     • Content similarity
     • Mentioned people/companies
     • Topic alignment
   • Confidence: Medium (requires confirmation)
   • Present top 1-2 matches to user
3. If uncertain:
   • Confidence: Low
   • Ask user: "Where should this update go? Suggestions: [1] [Project A], [2] [Project B], [3] Daily note, [4] Skip"

Action:

1. Read destination project file
2. Find or create ## Notes or ## Updates section
3. Append with timestamp:

   **YYYY-MM-DD:** [Update text]

Known project mappings (for reference, not hardcoded):

• Legata-related → 02_Projects/Job Search/Companies/Legata/Legata Index.md or relevant Legata subfolder file
• HPM website → 02_Projects/P - HPM Website.md
• Job search general → 02_Projects/Job Search/P - Job Search Strategic Project (Full Version).md
• Dossier product → 02_Projects/Project Backlog/P - The Dossier/Dossier Index.md

Type 4: New Opportunities

Pattern detection:

• Income/revenue mentions: "make money", "side hustle", "revenue", "monetization", "$X/month", "earn", "income"
• Business ideas: "business idea", "startup idea", "product idea", "service opportunity", "could sell"
• Opportunity language: "opportunity", "could build", "niche", "market gap", "untapped market"
• Action verbs (business context): "launch", "start", "build [business]", "sell", "offer", "charge"
• Market observations: "noticed people need X", "pain point", "would pay for"

Examples:

• "Build AI tool for property managers - could charge $50/month"
• "Side hustle idea: automated LinkedIn outreach service"
• "Noticed gap in market for X - opportunity to build Y"
• "Could make $2K/month doing freelance AI consulting"
• "New business opportunity: Airbnb management service"

Destination: 02_Projects/P - New Opportunities - discovery.md → Raw Leads section

Confidence:

• High: Clear business/income language + specific idea
• Medium: Mentions building something with business potential
• Low: Ambiguous (might just be a general thought)

Action:

1. Read P - New Opportunities - discovery.md
2. Find the ## 📥 Raw Leads section
3. Append in format:

   - [ ] **[Opportunity Name]:** [Description] [Source/Context if provided] [Added: YYYY-MM-DD]

4. If user provided links or references, include them in description

Note: If an item mentions both an opportunity AND has a URL, treat as opportunity (not link). The URL is context for the opportunity.

Type 5: General Thoughts

Pattern detection:

• Everything else that doesn't match above types
• Reflections, ideas, observations
• Not action-oriented
• No clear project association
• No business/income intent

Destination: Today's daily note at 99_System/Daily Notes/YYYY-MM-DD.md

Confidence:

• High: Short thought (<2 sentences)
• Medium: Substantial content (might warrant its own note)

Action:

1. Get today's date
2. Create or read daily note file
3. Find or create ## Notes section
4. If substantial (>3 sentences), ask: "Create new note or add to daily note? [1] Daily note, [2] New note in Inbox"
5. Append with timestamp if adding to daily note

Routing Format

For each item, output:

**Item 1/X:** [Content preview (first 50-100 chars)]
Type: [Link/Task/Project Update/New Opportunity/Thought]
Destination: [File path]
Confidence: [High/Medium/Low]

[If Medium or Low, show options and wait for user response]

User responses during triage:

• y or yes → Proceed with routing
• n or no → Skip item (leave in inbox)
• skip → Same as 'no', move to next
• remove → Delete item without routing
• stop → End session, keep remaining items
• Force routes:
  • daily note → Route to today's daily note
  • explore → Route to explore queue
  • tasks → Route to task inbox
  • Custom destination: file: [path] → Route to specified file

Project Matching Algorithm

When classifying Project Updates without explicit wikilinks:

1. Read Project Index:

   Read: 02_Projects/Project Index.md
   Extract: Active project names and file paths

2. Semantic Analysis:
   • Compare item text to project names/descriptions
   • Check for people names (cross-reference People Index if needed)
   • Check for company names
   • Look for domain alignment (job search, tech, property management, etc.)
3. Confidence Assessment:
   • High (≥0.8): Clear match, multiple signals align
   • Medium (0.5-0.7): Plausible match, some ambiguity
   • Low (<0.5): Multiple possible destinations or no clear match
4. Present Decision:
   • High: Show destination, ask quick confirm
   • Medium: Show top 2 suggestions, let user pick
   • Low: Ask user directly with 3-4 options

Archive Format

After routing each item, append to 05_Archives/Inbox Triage History.md:

## YYYY-MM-DD

- [x] [Item preview (first 50 chars)] → [[Destination]] | Type: [type] | Confidence: H/M/L

Group entries by date. Create date header if it doesn't exist.

Updating 00_INBOX.md

After successfully routing an item:

1. Read current inbox to get exact text
2. Remove the processed item line
3. Write updated inbox back
4. Move to next item

After skipping or removing:

• Skip: Leave in inbox, process next item
• Remove: Delete line, don't archive, process next item

Summary Output

After processing all items, output:

**Triage Summary:**

✓ Routed 6 items:
  - 2 links → Explore queue
  - 1 task → Task inbox
  - 1 project update → Legata Index (High confidence)
  - 1 new opportunity → Opportunities pipeline
  - 1 thought → Today's daily note

⊘ Skipped: 1 item
⊘ Removed: 1 item

Inbox now: 2 items remaining

Integration with Daily/Weekly Reviews

When called from /day:

• After processing task inbox, check universal inbox
• If >0 items: "You have X items in inbox. Triage now? (y/n)"
• If yes: Process 2-3 items max (quick triage)
• Keep daily check-in focused

When called from /week:

• During weekly review, check universal inbox
• If >5 items: "You have X items in inbox. Triage now? (y/n)"
• If yes: Offer /triage all or process interactively
• Don't force triage, keep review flow smooth

Example Workflow

User: /triage

Claude: You have 6 items in inbox. Process: [number] or 'all'

User: all

Claude:

**Item 1/6:** https://claude.ai/docs/intro-to-claude
Type: Link
Destination: 01_Inbox/00_EXPLORE.md → Unprocessed
Confidence: High

✓ Routed to explore queue

---

**Item 2/6:** - [ ] Follow up with Alesia about Legata timeline
Type: Task
Destination: 01_Inbox/01_TASKS.md → Open
Confidence: High

✓ Routed to task inbox

---

**Item 3/6:** Met with Bryan today - he wants to move faster on content strategy
Type: Project Update
Destination: 02_Projects/Job Search/Companies/Legata/Legata Index.md
Confidence: High (mentions Bryan, Legata-related)

Proceed? (y/n)

User: y

✓ Appended to Legata Index → Notes section

---

**Item 4/6:** Side hustle idea - build automated expense tracking for Airbnb hosts, could charge $30/month
Type: New Opportunity
Destination: 02_Projects/P - New Opportunities - discovery.md → Raw Leads
Confidence: High (clear business idea with pricing)

✓ Added to opportunities pipeline

---

**Item 5/6:** Need better morning routine
Type: Thought
Destination: 99_System/Daily Notes/2026-02-13.md → Notes
Confidence: High

✓ Added to today's daily note

---

**Item 6/6:** Quick thought: Need to think through Q2 goals
Type: Thought
Destination: 99_System/Daily Notes/2026-02-13.md → Notes
Confidence: Medium (might be worth dedicated note)

Create new note or add to daily note? [1] Daily note, [2] New note

User: 1

✓ Added to today's daily note

---

**Item 7/7:** https://www.reddit.com/r/productivity/comments/abc123
Type: Link
Destination: 01_Inbox/00_EXPLORE.md → Unprocessed
Confidence: High

✓ Routed to explore queue

---

**Triage Summary:**

✓ Routed 7 items:
  - 2 links → Explore queue
  - 1 task → Task inbox
  - 1 project update → Legata Index
  - 1 new opportunity → Opportunities pipeline
  - 2 thoughts → Daily note (2026-02-13)

Inbox now: 0 items (clear!)

Edge Cases

Multiple tasks in one line:

• Process as single task
• Suggest splitting if detected: "This looks like multiple tasks. Split into separate items? (y/n)"

Links with context: Example: "Interesting article about AI: https://example.com"

• Extract just the URL for explore queue
• Treat context as a thought if substantial

Opportunities with URLs: Example: "Build a SaaS for X - could make $5K/month https://competitor-example.com"

• Treat as opportunity (not link)
• Include URL in the opportunity description as context/research

Wikilinks without clear content: Example: "[[Legata Index]]"

• Ask: "What would you like to note about Legata? Or skip?"

URLs without protocol: Example: "www.example.com"

• Treat as link, normalize to https://

Ambiguous items: Example: "Theron"

• Ask: "Is this a task, note, or update? [1] Task (contact Theron), [2] Note (add to daily), [3] Skip"

File Locations

Post-Invocation

After triaging 5+ items or processing substantial project matches, suggest context clear to keep session efficient.