route

Builds a Context Brief from knowledge notes, past session notes, and ticket trackers before debugging.

6|1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill route-t-mercier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route
Source: https://github.com/t-mercier/ai-agents-orchestrator/tree/main/skills/route
Command: npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill route-t-mercier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a bug investigation or unfamiliar task, conclusions from past sessions are invisible in the codebase, forcing you to re-derive decisions that were already made. This Skill searches your space's knowledge notes, past session notes, and ticket trackers to surface what was already established before you open the code. ## Core Features & Use Cases - Knowledge note search: Resolves the correct notes vault from the session's space configuration, reads index files first, then searches notes, areas, and maps of content for query matches. - Past session recall: Searches session notes across configured roots to find previous work on the same subject, including decisions and next steps left behind. - Ticket tracker integration: Optionally queries Jira with summary-scoped JQL and fetches issues with comments, where root causes and resolutions typically live. - Use Case: Before debugging a recurring payment error, run the skill with the error string to get a Context Brief listing relevant knowledge notes, a past session that diagnosed the same failure, and the Jira ticket whose comments contain the root cause. ## Quick Start Ask the assistant to run /route with your ticket ID, topic, or error string to generate a Context Brief before investigating.

Frequently Asked Questions about route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find what past sessions concluded before debugging an issue?

Run the skill with a ticket ID, topic, or error string as the query. It searches your space's knowledge notes and past session notes, then assembles a Context Brief with conclusions, entry points, and relevant tracker tickets.

How to search Jira tickets I only commented on or triaged?

Search the summary field with domain nouns instead of filtering by assignee or reporter, since JQL has no commented-by field. Then fetch candidate issues with their comments, where root causes and resolutions are usually recorded.

Does the route skill modify my notes or tickets?

No, the skill is strictly read-only and never writes to any file or tracker. It only reads knowledge notes, session notes, and ticket data to assemble the Context Brief.

What happens when no past work matches my query?

The skill never returns an empty brief. It reports that the notes are cold on the subject and still suggests a starting point, such as the closest area or most likely repository, indicating the work is new ground.

Why does the skill read INDEX.md before search matches?

Index and conventions files explain how a vault is organized and what is recent, providing context that raw matches lack. They also reveal orphan notes that the search terms failed to surface.