clarification-protocol

Generate targeted clarifying questions for vague requirements before routing.

110|19|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-cto-team --skill clarification-protocol-alirezarezvani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarification-protocol
Source: https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/clarification-protocol
Command: npx skills add https://github.com/alirezarezvani/claude-cto-team --skill clarification-protocol-alirezarezvani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates 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.

Core Features & Use Cases

  • 2-3 clarifying questions per round to surface missing context.
  • Challenge assumptions to avoid misrouting and to guide decision making.
  • Provides example answers to guide users and expedite decisions.

Quick Start

Provide a vague or ambiguous request, and the protocol will generate 2-3 clarifying questions to sharpen the brief before routing to the appropriate agent.

Frequently Asked Questions about clarification-protocol

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

FAQPage Schema
How do I generate clarifying questions for vague requirements before routing?

Targeted clarifying questions resolve ambiguous requirements by challenging assumptions and extracting missing context before specialist routing. The protocol generates 2-3 focused questions per round to surface necessary details.

When do I need to use a clarification protocol for requirement routing?

A clarification protocol is needed when a request analyzer identifies ambiguity in requirements before routing. It prevents misrouting by resolving unclear requirements before delegating to specialist CTO agents.

What is the best way to prevent misrouting unclear requirements to specialist agents?

The best way to prevent misrouting unclear requirements is to use a structured framework that generates 2-3 clarifying questions per round. This challenges vague inputs and provides example answers to guide decision making before delegation.

Can I use challenge patterns to surface missing context in ambiguous requests?

Yes, challenge patterns surface missing context in ambiguous requests by generating focused questions. The protocol provides example answers to expedite decision making and sharpen the brief before specialist routing.

How many clarifying questions should I ask per round to resolve ambiguity?

Ask 2-3 clarifying questions per round to resolve ambiguity. This limited number ensures focused extraction of missing context without overwhelming the user before routing to the appropriate agent.