dev-team-guide

Route development agent requests to the correct handler by intent.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill dev-team-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-team-guide
Source: https://github.com/UsernameTron/Claude-Code-Kickstart/tree/main/plugins/claude-code-factory/skills/dev-team-guide
Command: npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill dev-team-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The invisible router centralizes intent detection and routing for application development agents, shielding users from routing internals and ensuring requests reach the appropriate handler every time.

Core Features & Use Cases

  • Silent intent routing: determine whether the user wants to browse dev recipes, create a specialist agent, assemble a dev team, or get agent recommendations, then route accordingly.
  • Domain-aware routing: enforce the project domain boundaries and dispatch to the correct sub-skills like recipes, concierge, or recommendations.
  • Safe, opaque UX: hides internal skill names, layer details, and routing logic from the user to keep interactions clean.

Quick Start

Ask for a development intent (e.g., browse dev recipes, build a dev team, or get agent recommendations) and let the router direct you to the right handler.

Frequently Asked Questions about dev-team-guide

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

FAQPage Schema
How do I route development agent requests to the correct handler?

Route development agent requests by defining a routing table with prioritized intents and signal phrases to dispatch requests like browsing dev recipes or assembling a dev team to the correct handler.

What is silent intent routing for dev-agent workflows?

Silent intent routing is a mechanism that detects user intents for development tasks and dispatches them to sub-skills like recipes or concierge without exposing internal routing logic or layer details.

Can I enforce domain boundaries when assembling a dev team workflow?

Yes, you can enforce domain boundaries by applying domain-aware routing rules that ensure development agent requests stay within project limits and dispatch to approved sub-skills securely.

What's the best way to hide internal skill names from users during agent routing?

Hide internal skill names by using a safe, opaque UX router that centralizes intent detection and shields users from routing internals, ensuring clean interactions without exposing layer details.

Do I need dependencies to use an invisible router for development agents?

No dependencies are required to use the invisible router for development agents, as it operates independently to detect intents and route requests to the appropriate handler.

Why does my dev-agent routing logic get exposed to the user?

Routing logic gets exposed when not using a silent router; implementing an invisible router centralizes intent detection and hides internal skill names and layer details from the user.