request-analyzer

Included with Lifetime

$97 forever

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.

Design

What this skill does


# 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](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:**
- [ ] Expected user/traffic scale
- [ ] Budget constraints
- [ ] Timeline requirements
- [ ] Team size and expertise
- [ ] Existing infrastructure

**For Validation Requests:**
- [ ] Current state or existing plan
- [ ] Business goals and constraints
- [ ] Timeline and resources
- [ ] Success criteria

## 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](classification-criteria.md) - Detailed routing logic
- [Buzzword Dictionary](buzzword-dictionary.md) - Common vague terms to challenge

Files: 3

Size: 14.6 KB

Complexity: 22/100

Category: Design

Source: https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts