skills.rest
aspelldenny
aspelldennyCOMMUNITY
Explore all skills by this author →
GitHub

route

Classify inbound requests into five routing lanes and generate a routing brief.

Updated Apr 4, 2026
Search Tags:#workflow#classification#route#inbound triage#architect handoff#sos-kit
One-click install
npx skills add https://github.com/aspelldenny/sos-kit --skill route-aspelldenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: route
Source: https://github.com/aspelldenny/sos-kit/tree/main/skills/attic/route
Command: npx skills add https://github.com/aspelldenny/sos-kit --skill route-aspelldenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and route every inbound request to the correct lane (code, marketing, design, strategy, or skip) so you can move quickly to downstream work without solving the issue itself.

Core Features & Use Cases

  • Quick inbound classification: decide the lane in under 30 seconds based on the input.
  • Produce a consistent routing brief for Architect handoff with fields like ROUTING, SOURCE, ONE-LINE, SUCCESS LOOKS LIKE, CONSTRAINTS, and RELATED CONTEXT.
  • Works across channels (email, chat, tickets) and supports multilingual entries.

Quick Start

Read the inbound, classify it into one lane, and generate the ROUTING brief for Architect.

Frequently Asked Questions about route

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

FAQPage Schema
How do I triage inbound requests into different workflow lanes?▼

To triage inbound requests, classify the input into one of five workflow lanes—code, marketing, design, strategy, or skip—within a strict 30-second decision window to determine routing rather than execution.

What is the best way to route user feedback and bug reports for downstream teams?▼

The best way to route user feedback and bug reports is to classify the inbound request and generate a consistent routing brief containing fields like SOURCE, ONE-LINE, and CONSTRAINTS for Architect handoff.

Can I use this inbound triage process for multilingual chat and email tickets?▼

Yes, you can use this inbound triage process for multilingual entries across multiple channels, including chat, email, and support tickets, to quickly classify and route requests.

Does this request classification workflow execute the task or just determine routing?▼

This request classification workflow determines routing rather than execution. It triages inbound requests into five lanes and outputs a routing brief for downstream teams to handle the actual execution.

What fields are included in the routing brief for Architect handoff?▼

The routing brief for Architect handoff includes consistent fields: ROUTING, SOURCE, ONE-LINE, SUCCESS LOOKS LIKE, CONSTRAINTS, and RELATED CONTEXT to ensure clear downstream communication.

Related Skills

Explore More Product & Management Skills→
chunkydotdevchunkydotdev
2

reply-classification

Classify inbound email replies by intent using header checks and keyword scoring.

Community
Advanced
EmasoftEmasoft
1

amama-role-routing

Route user requests to specialist agents via AMCOS with governance rules.

Community
Advanced
stepandelstepandel
4

pm-queue-handler

Route Linear tickets by labels, enrich with context, and assign to agents.

Community
Advanced
shogo-labsshogo-labs
12

chief-of-staff

Classify founder inbox items and route them to specialized reviewers.

Official
Advanced