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.
/plugin marketplace add alirezarezvani/claude-cto-team/plugin install cto-team@cto-team-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
buzzword-dictionary.mdclassification-criteria.mdClassifies 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:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.