/triage

name: triage
description: "Route orphaned inbox files and pull scattered `- [ ]` tasks into the right project/person/goal using current priorities. Use when the user says 'clean up my inbox', 'triage', 'sort out these notes'. Also use proactively when `00-Inbox/` is piling up. Not for updating notes from meetings; use `process-meetings`."
model_hint: fast

Cleanup and routing tool that finds standalone files and scattered tasks, then suggests where they belong using your current strategic context (Week Priorities + Quarterly Goals).

Execution Style

This skill handles quick decisions. Be concise. Don't over-analyze. Make a routing decision and move on. Target: <2 seconds of thinking per item.

What It Does

• **Files**: Routes standalone files in `00-Inbox/` to projects, person pages, or resource folders
• **Tasks**: Finds unchecked `- [ ]` tasks scattered across notes and routes them appropriately
• **Strategic**: Uses your Week Priorities and Quarterly Goals to inform routing confidence

Usage

• `/triage` - Process everything (files + tasks)
• `/triage files` - Organize standalone files only
• `/triage tasks` - Extract and route tasks only

Arguments

$MODE: Optional. "files" | "tasks" | "all". Default: "all"

---

Step 0: Load Strategic Context & Structure Discovery

Before processing inbox items, load strategic context and build an index of existing entities. This makes triage strategically aware and enables intelligent routing.

0. Load Strategic Context

Read these files to understand current priorities:

1. **Week Priorities**: `02-Week_Priorities/Week_Priorities.md`

• Extract this week's Top 3 focus items
• Note any specific projects/people mentioned
• Capture keywords and themes

2. **Quarterly Goals**: `01-Quarter_Goals/Quarter_Goals.md`

• Extract current quarter's goals
• Note associated projects and outcomes
• Capture keywords and themes

This context will inform routing decisions - entries matching current priorities get higher confidence scoring and are surfaced first.

1. Scan Projects

List all files in `04-Projects/`:

• Extract project name from filename (convert underscores to spaces)
• Read frontmatter if present for description, status, pillar
• Build index: `{ name, path, description, status, pillar }`

2. Scan People

List all files in `05-Areas/People/External/` and `05-Areas/People/Internal/`:

• Extract name from filename
• Read frontmatter/metadata table for role, company
• Build index: `{ name, path, company, role, type: internal|external }`

3. Scan Role-Specific Areas

List any additional folders under `05-Areas/` that aren't People or Career:

• These may be role-specific areas created during setup (e.g., Accounts/, Team/, Content/)
• Extract relevant names from filenames
• Build index: `{ name, path, type: area_type }`

4. Read Pillars

Parse `System/pillars.yaml`:

• Extract pillar names, descriptions, and keywords
• These inform categorization when no entity match is found

---

Step 0.5: Semantic Matching Enhancement (if QMD available)

**This step activates automatically when QMD is installed.** It dramatically improves routing accuracy by matching inbox items to goals, projects, and people by **meaning**, not just keywords.

Check if QMD MCP tools are available by calling the `status` tool (QMD MCP). **If available:**

After loading strategic context (Step 0), enhance matching with semantic search:

1. **For each inbox item**, run:

   query(query="[item title + first 100 words of content]", limit=5)

This finds vault content related by meaning. "Email about onboarding flow" matches "Q1 goal: improve activation rate" even though they share no keywords.

2. **For task deduplication**, use semantic similarity instead of keyword overlap:

   query(query="[task description]", limit=3)

Catches semantic duplicates: "Review Q1 metrics" detected as duplicate of "Check quarterly pipeline numbers".

3. **For goal alignment scoring**, run:

   query(query="[item content]", limit=3)

against quarterly goals and weekly priorities. Items semantically related to active goals get a +25 confidence boost.

**How this changes matching:**

| Aspect | Without QMD (keyword) | With QMD (semantic) | |--------|----------------------|---------------------| | Goal matching | Exact keyword overlap only | Meaning-based: "churn analysis" matches "retention goal" | | Duplicate detection | >60% string similarity | Semantic similarity: different words, same intent | | Person matching | Name must appear in text | Role/title references found: "the sales VP" → Sarah Chen | | Project matching | Project name in filename | Thematic connection: "pricing update" → "Acme Deal" project |

**Merge semantic scores with entity scores** from Step 0. The combined confidence determines routing priority.

**If QMD is not available:** Skip silently. The standard keyword-based matching in the steps below handles routing with existing patterns.

---

Mode: Files

Organize standalone files in the `00-Inbox/` folder by suggesting where they belong.

Process

1. **Scan 00-Inbox/**

• List all files (exclude Week Priorities.md, README.md)
• Read each file's content

2. **Match Against Strategic Context & Entities**

For each inbox file, check in this order:

| Check | Match Criteria | Action | Confidence Boost | |-------|---------------|--------|------------------| | **Week Priority match** | Content relates to this week's Top 3 priorities | Route to associated project/person, flag as HIGH priority | +30 points | | **Quarterly Goal match** | Content relates to current quarter's goals | Route to associated project, flag as strategic | +20 points | | **Project match** | File mentions project name, or filename contains project reference | Route to specific project file | +10 points if also matches priority | | **Person match** | File is about a specific person, contains t