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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Classifies incoming requests to enable intelligent routing and identify clarification needs before delegating to specialist agents.
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 |
| 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 |
| 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 |
Scan for buzzwords that require clarification. See buzzword-dictionary.md for the complete list.
Common red flags:
Check for required context based on request type:
For Design Requests:
For Validation Requests:
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]
User: "I want to add AI capabilities to my app"
Analysis:
User: "Design a real-time notification system for 100K users, using our existing PostgreSQL database and Node.js backend"
Analysis:
User: "Here's my Q2 roadmap - migrate to microservices, add real-time features, and launch mobile app. Thoughts?"
Analysis:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.
The English summary is being prepared. Showing the original description.
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.
The English summary is being prepared. Showing the original description.
Identify and challenge implicit assumptions in plans, proposals, and technical decisions. Use when strategic-cto-mentor needs to surface hidden assumptions and wishful thinking before they become costly mistakes.
The English summary is being prepared. Showing the original description.
Generate targeted clarifying questions (2-3 max) that challenge vague requirements and extract missing context. Use after request-analyzer identifies clarification needs, before routing to specialist agents. Helps cto-orchestrator avoid delegating unclear requirements.
The English summary is being prepared. Showing the original description.
Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.
The English summary is being prepared. Showing the original description.
Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect). Use after clarification is complete, before routing to specialist agents. Ensures agents receive complete context for effective work.
The English summary is being prepared. Showing the original description.