Request Analyzer
Classifies incoming requests to enable intelligent routing and identify clarification needs before delegating to specialist agents.
When to Use
- When receiving a new user request that needs classification
- When determining which specialist agent should handle a request
- When identifying if requirements are too vague to proceed
- When detecting buzzwords that need to be challenged
Analysis Framework
Step 1: Detect Intent
Classify the primary intent:
| Intent |
Indicators |
Route |
| Strategic |
"roadmap", "strategy", "plan", "prioritize", "decide" |
May need validation |
| Implementation |
"build", "create", "implement", "design", "architect" |
Design work |
| Debugging |
"fix", "broken", "error", "slow", "not working" |
Debug/investigate |
| Documentation |
"document", "explain", "describe", "write docs" |
Documentation |
Step 2: Classify Request Type
| Type |
Key Phrases |
Primary Agent |
| Design |
"How should I build...", "What architecture...", "Design a system..." |
cto-architect |
| Validate |
"Is this plan solid?", "Thoughts on...", "Review my roadmap..." |
strategic-cto-mentor |
| Debug |
"Why is X slow?", "Fix this error...", "Troubleshoot..." |
debug-helper |
| Document |
"Write documentation for...", "Explain how..." |
docs-writer |
| Review |
"Review this code...", "Check for issues..." |
code-reviewer |
Step 3: Assess Complexity
| Complexity |
Characteristics |
Execution Pattern |
| Single |
Clear scope, one domain, obvious routing |
Direct to one agent |
| Sequential |
Multiple phases, depends on previous output |
Agent chain |
| Parallel |
Independent domains, can run simultaneously |
Multiple agents in parallel |
Step 4: Identify Vague Terms
Scan for buzzwords that require clarification. See buzzword-dictionary.md for the complete list.
Common red flags:
- "AI-powered" - What specific AI capability?
- "scale" - What numbers? From what to what?
- "fast" / "soon" - What timeline exactly?
- "simple" - Simple for whom? What constraints?
- "modern" - What specific technologies?
Step 5: Detect Missing Context
Check for required context based on request type:
For Design Requests:
For Validation Requests:
Output Format
Provide analysis in this structure:
## Request Analysis
**Intent**: [strategic | implementation | debugging | documentation]
**Type**: [design | validate | debug | document | review]
**Complexity**: [single | sequential | parallel]
### Vague Terms Detected
- "[term]" - needs clarification: [what to ask]
### Missing Context
- [missing information item]
### Suggested Routing
**Primary Agent**: [agent name]
**Rationale**: [why this agent]
### Clarification Needed
[yes/no] - [brief explanation]
### Recommended Next Step
[what to do next - clarify or delegate]
Examples
Example 1: Vague Request
User: "I want to add AI capabilities to my app"
Analysis:
- Intent: Implementation
- Type: Design
- Complexity: Unknown (needs clarification)
- Vague Terms: "AI capabilities" - What specific problem are we solving?
- Missing Context: Scale, budget, timeline, team, existing stack
- Clarification Needed: Yes
- Next Step: Use clarification-protocol before routing
Example 2: Clear Design Request
User: "Design a real-time notification system for 100K users, using our existing PostgreSQL database and Node.js backend"
Analysis:
- Intent: Implementation
- Type: Design
- Complexity: Single
- Vague Terms: None
- Missing Context: Timeline, budget (nice to have but not blocking)
- Suggested Routing: cto-architect
- Clarification Needed: No (can proceed with optional clarification)
Example 3: Validation Request
User: "Here's my Q2 roadmap - migrate to microservices, add real-time features, and launch mobile app. Thoughts?"
Analysis:
- Intent: Strategic
- Type: Validate
- Complexity: Single
- Vague Terms: None
- Missing Context: Team size, current architecture state
- Suggested Routing: strategic-cto-mentor
- Clarification Needed: Mild (some context helpful but not blocking)
References
- Classification Criteria - Detailed routing logic
- Buzzword Dictionary - Common vague terms to challenge
1---2name: request-analyzer3description: Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification. Use when cto-orchestrator receives new requests that need classification before routing to specialist agents.4---56# Request Analyzer78Classifies incoming requests to enable intelligent routing and identify clarification needs before delegating to specialist agents.910## When to Use1112- When receiving a new user request that needs classification13- When determining which specialist agent should handle a request14- When identifying if requirements are too vague to proceed15- When detecting buzzwords that need to be challenged1617## Analysis Framework1819### Step 1: Detect Intent2021Classify the primary intent:2223| Intent | Indicators | Route |24|--------|------------|-------|25| **Strategic** | "roadmap", "strategy", "plan", "prioritize", "decide" | May need validation |26| **Implementation** | "build", "create", "implement", "design", "architect" | Design work |27| **Debugging** | "fix", "broken", "error", "slow", "not working" | Debug/investigate |28| **Documentation** | "document", "explain", "describe", "write docs" | Documentation |2930### Step 2: Classify Request Type3132| Type | Key Phrases | Primary Agent |33|------|-------------|---------------|34| **Design** | "How should I build...", "What architecture...", "Design a system..." | cto-architect |35| **Validate** | "Is this plan solid?", "Thoughts on...", "Review my roadmap..." | strategic-cto-mentor |36| **Debug** | "Why is X slow?", "Fix this error...", "Troubleshoot..." | debug-helper |37| **Document** | "Write documentation for...", "Explain how..." | docs-writer |38| **Review** | "Review this code...", "Check for issues..." | code-reviewer |3940### Step 3: Assess Complexity4142| Complexity | Characteristics | Execution Pattern |43|------------|-----------------|-------------------|44| **Single** | Clear scope, one domain, obvious routing | Direct to one agent |45| **Sequential** | Multiple phases, depends on previous output | Agent chain |46| **Parallel** | Independent domains, can run simultaneously | Multiple agents in parallel |4748### Step 4: Identify Vague Terms4950Scan for buzzwords that require clarification. See [buzzword-dictionary.md](buzzword-dictionary.md) for the complete list.5152**Common red flags:**53- "AI-powered" - What specific AI capability?54- "scale" - What numbers? From what to what?55- "fast" / "soon" - What timeline exactly?56- "simple" - Simple for whom? What constraints?57- "modern" - What specific technologies?5859### Step 5: Detect Missing Context6061Check for required context based on request type:6263**For Design Requests:**64- [ ] Expected user/traffic scale65- [ ] Budget constraints66- [ ] Timeline requirements67- [ ] Team size and expertise68- [ ] Existing infrastructure6970**For Validation Requests:**71- [ ] Current state or existing plan72- [ ] Business goals and constraints73- [ ] Timeline and resources74- [ ] Success criteria7576## Output Format7778Provide analysis in this structure:7980```81## Request Analysis8283**Intent**: [strategic | implementation | debugging | documentation]84**Type**: [design | validate | debug | document | review]85**Complexity**: [single | sequential | parallel]8687### Vague Terms Detected88- "[term]" - needs clarification: [what to ask]8990### Missing Context91- [missing information item]9293### Suggested Routing94**Primary Agent**: [agent name]95**Rationale**: [why this agent]9697### Clarification Needed98[yes/no] - [brief explanation]99100### Recommended Next Step101[what to do next - clarify or delegate]102```103104## Examples105106### Example 1: Vague Request107108**User**: "I want to add AI capabilities to my app"109110**Analysis**:111- **Intent**: Implementation112- **Type**: Design113- **Complexity**: Unknown (needs clarification)114- **Vague Terms**: "AI capabilities" - What specific problem are we solving?115- **Missing Context**: Scale, budget, timeline, team, existing stack116- **Clarification Needed**: Yes117- **Next Step**: Use clarification-protocol before routing118119### Example 2: Clear Design Request120121**User**: "Design a real-time notification system for 100K users, using our existing PostgreSQL database and Node.js backend"122123**Analysis**:124- **Intent**: Implementation125- **Type**: Design126- **Complexity**: Single127- **Vague Terms**: None128- **Missing Context**: Timeline, budget (nice to have but not blocking)129- **Suggested Routing**: cto-architect130- **Clarification Needed**: No (can proceed with optional clarification)131132### Example 3: Validation Request133134**User**: "Here's my Q2 roadmap - migrate to microservices, add real-time features, and launch mobile app. Thoughts?"135136**Analysis**:137- **Intent**: Strategic138- **Type**: Validate139- **Complexity**: Single140- **Vague Terms**: None141- **Missing Context**: Team size, current architecture state142- **Suggested Routing**: strategic-cto-mentor143- **Clarification Needed**: Mild (some context helpful but not blocking)144145## References146147- [Classification Criteria](classification-criteria.md) - Detailed routing logic148- [Buzzword Dictionary](buzzword-dictionary.md) - Common vague terms to challenge
Alireza Rezvani