architect-router

Route architecture inquiries to the appropriate architecture lane.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill architect-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-router
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/architect-router
Command: npx skills add https://github.com/Ocean326/Agents --skill architect-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a stable front door for architecture work, routing requests to the most appropriate architecture lane to avoid misrouting and fragmentation.

Core Features & Use Cases

  • Stable architecture entry point that classifies and routes to lanes such as architect, architecture-governance, codebase-architecture, spec-driven-architecture, ddd-clean-architecture, agent-systems-architecture, and architecture-docs-review.
  • Routing table and decision rules to determine the appropriate lane based on task characteristics.
  • Direct-entry support for single-lane tasks to minimize routing overhead and latency.

Quick Start

Ask the Architect Router to route your architecture problem to the most appropriate lane and provide the recommended next action.

Frequently Asked Questions about architect-router

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

FAQPage Schema
How do I route a broad system design inquiry to the correct architecture lane?

The Architect Router solves architecture misrouting by acting as a stable front door, evaluating task characteristics against a routing table to recommend the most appropriate architecture lane and next action.

How does the routing mechanism work for ambiguous architecture governance tasks?

The routing mechanism applies decision rules and direct-entry exceptions to classify ADR governance and codebase architecture tasks, matching task characteristics to specific lanes to prevent fragmentation.

Can I use direct-entry routing for single-lane architecture tasks to reduce latency?

Yes, you can use direct-entry support for single-lane architecture tasks to minimize routing overhead and latency, bypassing full routing table evaluation when the exact lane is already clear.

What is the best way to prevent fragmentation across multiple architecture design reviews?

The best way to prevent fragmentation is to use a stable architecture entry point that classifies and routes design review inquiries, ensuring all tasks flow through consistent decision rules before reaching a specialized lane.

Do I need to specify a target lane for agent-systems-architecture tasks if I am unsure?

No, you do not need to specify a target lane when unsure; the Architect Router evaluates agent-systems-architecture tasks and recommends the most appropriate lane along with the next action.