Triage

<!-- Generated from `.claude/skills/triage/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->

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:

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 their name prominently	Route to person page OR suggest linking	+10 points if person mentioned in priorities
   Company match	File mentions company name, or attendees from known domain	Route to company page in 05-Areas/Companies/	Base confidence
   Pillar keyword match	Content matches pillar keywords	Tag with pillar, suggest relevant category	Base confidence
   No entity match	None of the above	Fall back to category routing	Low confidence

3. Category Fallback Rules

   When no specific entity matches, use these rules:

   Destination	Criteria
   04-Projects/	Has deadline, specific outcome, time-bound
   05-Areas/[specific area]/	Belongs to a role-specific area (Accounts/, Team/, Content/)
   05-Areas/People/	Person-specific information
   06-Resources/	Reference material, knowledge, learnings
   07-Archives/	Old/completed, no longer active
   Delete	No value, redundant, or temporary

4. Present Suggestions with Strategic & Entity Context

   Show what was matched, prioritizing items that align with current priorities:

   File: [filename]
   Strategic Context: [Week Priority/Q Goal if matched]
   Match: [entity type] → [specific entity name]
   Destination: [exact path]
   Confidence: [high/medium/low] ([score]/100)
   Action: [suggested action]

   Sort order:

   1. Items matching Week Priorities (highest confidence first)
   2. Items matching Quarterly Goals
   3. Items matching known entities (projects, people, companies)
   4. Generic category routing

   Flag misalignments:

   • If multiple entries relate to something NOT in priorities/goals, surface it: "You've captured 5 items about [topic]. Consider adding to priorities?"

5. Execute with Confirmation

   • Show full plan
   • Wait for user approval
   • Move files using mv (not copy)
   • For merges, append content to existing file

---