owner-routing
Internal process for the owner-router agent. Defines the step-by-step procedure for determining likely bug owners using strict 6-level routing precedence with staleness detection. Not user-invocable — loaded by the owner-router agent through its skills frontmatter.
What this skill does
# Owner Routing Process Step-by-step procedure for determining the most likely owner/team for each bug cluster using strict 6-level precedence with staleness detection and override memory. ## Overview Loaded by the `owner-router` agent inside the `x-bug-triage` plugin. Walks each open bug cluster through a deterministic six-level routing precedence (service-owner → oncall → CODEOWNERS → recent assignees → recent committers → fallback mapping), applies confidence modifiers, detects stale signals, and produces a ranked routing recommendation. Honors prior routing overrides recorded in cluster memory before consulting any signal source. ## Prerequisites - Cluster table populated upstream by the bug-clustering stage - Routing config available at `config/routing.json` (precedence modifiers, staleness threshold) - Triage MCP server reachable for `mcp__triage__lookup_*` tool calls - Repos in the cluster's product_surface have a configured surface→repo mapping ## Instructions ### Step 1: Check Overrides First For each cluster, check if a routing_override exists from a prior run: - If found: use the override (confidence 1.0, source "routing_override"), skip precedence lookup - Log the override application to audit ### Step 2: Query Sources in Precedence Order For each cluster without an override, query sources strictly in order: | Level | Source | Tool | Base Confidence | |-------|--------|------|----------------| | 1 | Service owner | `mcp__triage__lookup_service_owner` | 1.0 | | 2 | Oncall | `mcp__triage__lookup_oncall` | 0.9 | | 3 | CODEOWNERS | `mcp__triage__parse_codeowners` | 0.8 | | 4 | Recent assignees (30d) | `mcp__triage__lookup_recent_assignees` | 0.6 | | 5 | Recent committers (14d) | `mcp__triage__lookup_recent_committers` | 0.5 | | 6 | Fallback mapping | Config lookup | 0.3 | Stop at the first level that returns a valid team or assignee. ### Step 3: Apply Confidence Modifiers Multiply each result's confidence by the precedence modifier from routing_config. ### Step 4: Detect Staleness Flag any routing signal older than the staleness threshold (default 30 days): - Mark the result as stale with the number of days - Reduce confidence accordingly - Stale signals are still usable but should be noted in output ### Step 5: Build Recommendation Using `lib.buildRoutingRecommendation()`: - Rank valid results by level (lowest level = highest priority) - Set top_recommendation to the best result - If no valid results: set uncertainty=true with reason "Routing: uncertain — no routing signals available. Manual assignment required." ## Output - `cluster_routing` rows with ranked candidates (team/assignee, source level, confidence, staleness flag) - `top_recommendation` field set on each cluster (or null with uncertainty=true if no signals) - Audit-event rows recording every override application, source query, and stale-signal flag ## Error Handling - Source query failure (transient API error): log, skip that level, fall through to next - All six levels return empty: emit uncertainty=true with the standard reason, do not raise - Override exists but references a non-existent team: log warning, fall back to precedence walk - Staleness detection unavailable (missing timestamp): treat signal as fresh, flag as "unknown_age" ## Examples Triggered automatically by the owner-router agent after clusters are produced. Typical run output for a 12-cluster batch: "12 clusters routed — 1 via override, 4 via service-owner, 3 via oncall, 2 via CODEOWNERS, 2 via recent committers, 0 via fallback (1 stale signal flagged)". ## Resources Load routing precedence rules: ``` !cat skills/x-bug-triage/references/routing-rules.md ``` Load escalation trigger definitions: ``` !cat skills/x-bug-triage/references/escalation-rules.md ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.