request-analyzer

Classifies incoming user requests to determine intent, routing type, and required clarifications.

110|19|Updated Dec 4, 2025

Search Tags:#routing #clarification #complexity #analyze #intent-detection #request-classification #buzzwords

Ready to run

npx skills add https://github.com/alirezarezvani/claude-cto-team --skill request-analyzer-alirezarezvani

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: request-analyzer
Source: https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer
Command: npx skills add https://github.com/alirezarezvani/claude-cto-team --skill request-analyzer-alirezarezvani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze incoming user requests to detect intent, routing type, complexity, and identify vague requirements or buzzwords that need clarification for accurate routing to specialist agents.

Core Features & Use Cases

Intent detection: determine whether a request is strategic, implementation, debugging, or documentation.
Type classification: map requests to design, validate, debug, document, or review tasks for appropriate agents.
Complexity assessment: gauge whether the request is single, sequential, or parallel in scope for routing decisions.
Buzzword detection: flag vague terms using a centralized dictionary to surface needed clarifications.
Context extraction: surface required details such as scale, constraints, and timelines to reduce back-and-forth.
Use Case: when new requests arrive at the cto-orchestrator, route to the right specialist with clear objectives.

Quick Start

Submit a new request to the cto-orchestrator and let the Request Analyzer classify its intent, type, complexity, and required clarifications.

Frequently Asked Questions about request-analyzer

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

FAQPage Schema

How do I classify incoming software requests to determine intent and routing type?▼

You classify incoming software requests by analyzing intent, categorizing the request type into design, validate, debug, document, or review, and assessing complexity to route tasks to the appropriate specialist agents.

What is the best way to detect vague buzzwords in software requirements?▼

Detecting vague buzzwords in software requirements involves flagging ambiguous terms using a centralized buzzword dictionary, which surfaces needed clarifications and reduces back-and-forth communication during agent routing.

How do I assess request complexity for parallel or sequential agent routing?▼

Assessing request complexity involves gauging whether the scope is single, sequential, or parallel, which directly informs routing decisions to ensure the correct specialist agents handle the workload.

How do I extract required context like constraints and timelines from user requests?▼

Extracting required context from user requests involves surfacing specific details such as scale, constraints, and timelines, ensuring routing decisions have clear objectives and missing information is identified.

Can I use intent detection to route strategic versus implementation tasks differently?▼

Yes, intent detection determines whether a request is strategic, implementation, debugging, or documentation, allowing the system to map requests to appropriate agents and route distinct task types accurately.

Does request classification work without providing additional context for missing requirements?▼

Request classification identifies missing context by flagging vague buzzwords and surfacing required details like constraints, but you must provide the clarified information to achieve precise routing without back-and-forth.