topic-routerlisted

# Topic Router Every agent must use this skill before broad source exploration or edits in any repository. It routes the task through regin's **dense pattern index** (embedding retrieval + cross-encoder rerank) so the highest-signal pattern guidance is loaded before you touch the code. ## When to invoke (always) Run this skill at the start of **every** non-trivial repo turn, including: - **Bug fixes / debugging** — "fix X", "X is broken", "why does X fail", investigating a stack trace, reproducing an issue. - **Procedure / "how does it work" questions** — "how does X work", "what's the flow for Y", "explain the Z pipeline", "where is X handled". - **Code edits & refactors** — adding a feature, renaming, splitting, extracting, restructuring. - **Planning** — before drafting an implementation plan, before entering plan mode, before designing a change. - **Exploration** — when you'd otherwise reach for `grep`/`find`/`ls` to orient yourself. Skip only for trivial one-shot tasks where no procedure could apply (e.g. "echo this string", "what does `ls -la` mean"). ## Workflow 1. Extract 2-6 concise search keywords from the user's request, changed files, repo area, feature name, or workflow name. Prefer stable nouns and domain terms; do not paste the full goal sentence — dense rerank works best on tight lexical queries. Example: use `topics workspace delete`, not `I need to improve the delete flow in the topics workspace`. 2. Route those keywords through the dense pattern