commands-router

Route tasks to reasoning frameworks and sc:* command patterns via semantic routing.

7|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Zpankz/mcp-skillset --skill commands-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commands-router
Source: https://github.com/Zpankz/mcp-skillset/tree/main/commands-router
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill commands-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates routing of tasks to the appropriate reasoning frameworks and command patterns, reducing manual handoffs and context switching.

Core Features & Use Cases

  • Semantic routing: uses reasoning-index to map tasks to sc:* commands and patterns.
  • Workflow orchestration: coordinates development tasks, brainstorming, architecture decisions, and PRD-like workstreams.
  • Integration-ready: coordinates with commands-db, skill-db, and meta-router for end-to-end execution.

Quick Start

Describe the task and invoke reasoning-index to derive the best sc:* commands for routing.

Frequently Asked Questions about commands-router

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

FAQPage Schema
How do I route development tasks to the correct reasoning frameworks automatically?

Routing development tasks to reasoning frameworks is achieved by using semantic routing to map operations to appropriate command patterns. This reduces manual handoffs by deriving the correct sc:* commands to ensure consistent execution paths for brainstorming and architecture decisions.

What is semantic routing for workflow orchestration and when is it needed?

Semantic routing for workflow orchestration is the process of mapping tasks to command patterns using a reasoning index. It is needed when coordinating complex workstreams like development tasks or architecture decisions to reduce context switching and ensure consistent execution paths.

How do I use a reasoning index to map tasks to command patterns?

To map tasks to command patterns, describe the task and invoke the reasoning index to derive the best sc:* commands for routing. This coordinates with skill databases and meta-routers to resolve, propose, and chain the correct commands for end-to-end execution.

Can I orchestrate architecture decisions and brainstorming workstreams without manual context switching?

Orchestrating architecture decisions and brainstorming without manual context switching is possible by using semantic routing to coordinate workstreams. The system integrates with command databases and meta-routers to automatically resolve and chain the necessary command patterns.

Do I need a commands database and meta-router to execute routed command chains?

A commands database and meta-router are required to resolve, propose, and chain the correct sc:* commands for end-to-end execution. These integrations enable the system to coordinate tasks across development, brainstorming, and architecture workstreams effectively.

What are the limitations of using semantic command routing for complex development tasks?

The limitation of semantic command routing is its strict dependency on external modules like reasoning-index, commands-db, skill-db, and meta-router to resolve and propose commands. Without these integrations, the system cannot derive or chain the correct command patterns for execution.