team-routing
Identifies the correct domain owner for a task or PR by analyzing file paths, branch names, and team workload.
Install
mkdir -p .claude/skills/team-routing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6512" && unzip -o skill.zip -d .claude/skills/team-routing && rm skill.zipInstalls to .claude/skills/team-routing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Detect domain from context and find appropriate team memberKey capabilities
- →Extract domain keywords
- →Query Notion databases
- →Check team availability
- →Assign reviewers
How it works
It scans context for keywords, queries databases for domain owners, and checks availability to assign reviewers.
Inputs & outputs
When to use team-routing
- →Auto-assigning PR reviewers
- →Identifying domain owners for bug fixes
- →Checking developer capacity for new tasks
- →Routing feature requests to the right team
About this skill
Team Routing Skill
Automatically detect domain from branch names or file paths and find the appropriate reviewer.
When to Use
- Push PR mode: auto-assign reviewer
- Init mode: show domain context
- Any mode needing domain owner lookup
Phases
Phase 1: Extract Keywords
Extract domain keywords from context:
From branch name:
feature/tables-filter → keywords: ["tables"]
fix/auth-token-expired → keywords: ["auth"]
chore/settings-refactor → keywords: ["settings"]
From changed files:
git diff --name-only origin/develop | head -20
Match file paths against known patterns:
apps/web/features/tables/→ "tables"apps/api/routes/auth/→ "auth"apps/web/features/settings/→ "settings"
Phase 2: Query Notion Domains Database
API-query-database: [Domains-DB-ID]
Filter: Keywords contains [extracted-keyword]
OR Codebase_Paths contains [file-pattern]
Expected result:
- Domain name
- Topology type (stream-aligned, platform, enabling, complicated-subsystem)
- Primary keywords
Phase 3: Query Team Capabilities
API-query-database: Team Capabilities
Filter: Primary_Domain matches [domain-name]
AND Availability = "Available"
Sort: Open_PR_Count ASC
Expected result:
- Person name
- GitHub handle
- Max Open PRs
- Current Open PR count
Phase 4: Check Availability
For each candidate:
- Query current open PRs:
gh pr list --state open --author [github_handle] --json number | jq length - Compare against Max_Open_PRs threshold
- Skip if at or over capacity
Phase 5: Fallback Logic
If no available primary owner:
- Backup Owners: Query Skills table for overlapping skills
- Skills Match: Match changed file extensions to skill file patterns
- No Match: Return warning: "No available reviewer found for domain [X]"
Output
Present findings as:
## Domain Detection
**Branch:** [branch-name]
**Detected Domain:** [domain-name]
**Topology:** [stream-aligned | platform | enabling | complicated-subsystem]
### Reviewer Assignment
**Primary Owner:** @[github_handle] ([person_name])
**Availability:** [Available | At capacity (X/Y PRs)]
**Assignment:** [Assigned | Fallback to @backup | No available reviewer]
Integration
This skill is invoked by:
push-pr.mdc- Phase 1.2 (Find Reviewer)init.mdc- Domain context display
Notion Databases Required:
- Domains (keywords, codebase paths)
- Team Capabilities (person, domain, availability, max PRs)
- Skills (file patterns for fallback matching)
When not to use it
- →Manual assignment
- →Non-domain based routing
Prerequisites
Limitations
- →Requires Notion database integration
How it compares
It automates reviewer selection based on domain topology and capacity instead of manual assignment.
Compared to similar skills
team-routing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| team-routing (this skill) | 1 | 7mo | Review | Intermediate |
| linear-ticket | 1 | 6mo | No flags | Intermediate |
| design-to-issues | 0 | 5mo | No flags | Advanced |
| team-workflow | 0 | 1mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by WellApp-ai
View all by WellApp-ai →You might also like
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
design-to-issues
cloverich
Creates a GitHub epic and child issues from a design document's implementation plan. Use when a design doc has a reviewed plan section ready to be converted into trackable work.
team-workflow
jevonsnotes
>
slack-proactive-intervention-patterns
krafton-ai
메모리에서 7가지 개입 기회 패턴을 감지하는 지식 베이스. 조사 제안, 스케줄링, 문서화, 초안 작성, 연결 조율, 예측적 제안, 루틴 자동화 패턴의 시그널과 점수 계산 방법.
task-master
sfc-gh-dflippo
AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.
agile-product-owner
davila7
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.