clarification

Controls when AI agents ask user questions during task execution.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/Dazlarus/karl-code --skill clarification-dazlarus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarification
Source: https://github.com/Dazlarus/karl-code/tree/main/.agents/skills/clarification
Command: npx skills add https://github.com/Dazlarus/karl-code --skill clarification-dazlarus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often interrupt users with excessive clarification questions or, conversely, make wrong assumptions on genuinely ambiguous requests. This Skill defines clear rules for when to ask questions versus when to proceed with reasonable assumptions, preventing question spam while avoiding costly misinterpretations. ## Core Features & Use Cases - Decision Framework: Provides explicit criteria for when to ask questions (high-impact architectural, security, or performance decisions) versus when to use reasonable defaults (standard patterns like pytest, black, or logging). - Question Formatting Rules: Enforces a single-question pattern with 2-4 options and brief tradeoff descriptions, avoiding open-ended or stacked questions. - Context-Aware Behavior: Adjusts questioning behavior by phase—planning, execution, investigation, and revision—so exploration is never interrupted mid-flow. - Use Case: When a user says "add caching", the agent recognizes this as ambiguous (in-memory vs Redis vs Memcached) and asks one structured question; when a user says "add tests", it proceeds directly with pytest. ## Quick Start Activate this skill so the agent only asks clarifying questions for genuinely ambiguous, high-impact decisions and uses stated assumptions otherwise.

Frequently Asked Questions about clarification

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

FAQPage Schema
How do I stop an AI agent from asking too many questions?▼

Apply a clarification policy that requires questions only for genuinely ambiguous, high-impact decisions such as architecture, security, or breaking changes. Straightforward requests like adding tests or logging should proceed with standard defaults like pytest or the logging module.

When should an AI coding assistant ask clarifying questions?▼

Ask only when the request is genuinely ambiguous and the decision is high-impact, such as choosing between caching backends, auth strategies, or architectural approaches. Trivial tasks and common patterns should use reasonable assumptions instead.

What is the best format for AI agent clarification questions?▼

Use a single question with 2-4 clearly described options, each including brief tradeoffs and a recommended choice when applicable. Avoid open-ended questions, stacked multi-question prompts, and interruptions during exploration.

How should an AI agent communicate assumptions instead of asking?▼

State the assumption explicitly in the plan output, for example noting that in-memory caching was assumed and inviting correction if Redis is needed. This keeps progress unblocked while remaining transparent and easy to revise.

When should clarification questions be avoided entirely?▼

Avoid questions during active exploration or execution, for straightforward requests like fixing a bug, and for standard patterns already established in the codebase such as formatters or test frameworks. Interrupting flow in these cases causes question spam.