aii-clarify

Resolves request ambiguity by asking targeted questions before executing tasks.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/maestroventures/aiintegrator --skill aii-clarify-maestroventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aii-clarify
Source: https://github.com/maestroventures/aiintegrator/tree/main/plugins/aii-blueprint/skills/aii-clarify
Command: npx skills add https://github.com/maestroventures/aiintegrator --skill aii-clarify-maestroventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Acting on a half-understood request wastes effort twice: once building the wrong thing, once redoing it. This Skill closes genuine gaps in a request before work begins, using the fewest questions possible, so the output matches what the user actually wanted. ## Core Features & Use Cases - Gap Detection: Scans requests for missing inputs, ambiguous readings, unstated scope, and hidden assumptions that would change the output. - Structured Questioning: Asks one question at a time with numbered options, a labeled recommendation, and a plain-language rationale so users can answer quickly. - Reset Loop: After any user correction or redirect, re-checks the next step for new ambiguity instead of assuming the path is clear. - Use Case: A user asks to "update the report." Instead of guessing, the Skill checks existing sources first, then asks which report, which sections, and what format — with a recommended default for each — before making any edits. ## Quick Start Ask the assistant to clarify my request before starting whenever the task has missing details or more than one reasonable interpretation.

Frequently Asked Questions about aii-clarify

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

FAQPage Schema
How do I get an AI assistant to ask clarifying questions before starting a task?

Use a clarification workflow that scans the request for missing inputs, ambiguous readings, and unstated scope, then asks only the questions that would change the output. Questions are asked one at a time with numbered options and a labeled recommendation.

How to avoid AI building the wrong thing from a vague request?

Detect gaps before execution: check existing sources and specs first, then ask pointed questions only for genuine unknowns. Each question should carry a recommended option so the user can confirm quickly instead of writing long explanations.

When should an AI assistant not ask clarifying questions?

Skip clarification when the request is already clear and self-contained, when the user already answered the question earlier in the session, or when an existing source or artifact answers it. Asking for the sake of asking adds friction without value.

What should I do after correcting an AI assistant mid-task?

Re-check the next step for new ambiguity rather than assuming the path is now clear. A correction often opens a fresh gap, so the clarification loop should re-run on the new direction until nothing material is unclear.

How many clarifying questions should be asked at once?

Ask one question per prompt, and if several are needed, state the count up front and ask them in order. Each question should include numbered options with the recommended choice listed first and a one-line reason.