adv-clarify

Generate Socratic questions to resolve ambiguity in engineering specifications.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-clarify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-clarify
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-clarify
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity in engineering requirements by applying a structured Socratic questioning methodology, preventing scope drift and ensuring clear acceptance criteria before development begins.

Core Features & Use Cases

  • Socratic Questioning: Automatically generates neutral, probing questions based on six distinct categories (Clarification, Assumptions, Evidence, Alternatives, Implications, Meta-questions).
  • Findings-Driven Resolution: Integrates directly with discovery and audit phases to process ambiguity findings and log resolutions.
  • Use Case: When a requirement like "make the dashboard fast" is proposed, the skill identifies the ambiguity and prompts the user to define specific latency metrics or performance thresholds.

Quick Start

Invoke the adv-clarify skill to process the current ambiguity findings and generate a set of Socratic questions to refine the project requirements.

Frequently Asked Questions about adv-clarify

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

FAQPage Schema
How do I clarify ambiguous requirements in a software specification?

Clarifying ambiguous requirements involves systematically probing assumptions and scope through structured Socratic questioning to convert vague specifications into actionable acceptance criteria.

What is a Socratic questioning framework for engineering requirements?

A Socratic questioning framework for engineering requirements is a structured methodology that generates neutral questions across six categories—such as assumptions, evidence, and implications—to probe scope and resolve ambiguity in technical specifications.

How do I define acceptance criteria for vague project requirements?

Defining acceptance criteria for vague requirements requires processing ambiguity findings through a structured discovery phase, identifying edge cases, and generating probing questions to establish measurable metrics and clear project boundaries.

What is the best way to resolve scope drift during the discovery phase?

Resolving scope drift during the discovery phase is best achieved by applying a systematic taxonomy of probing questions to challenge assumptions, evaluate alternatives, and solidify actionable acceptance criteria before implementation.

When do I need a structured methodology to resolve ambiguity in AI specs?

You need a structured methodology to resolve ambiguity in AI specs when a proposed requirement lacks specific metrics, such as defining performance thresholds, and requires neutral, evidence-based dialogue to prevent scope drift.

Can I use Socratic questioning to process audit findings and log resolutions?

Yes, you can use Socratic questioning to process audit findings by integrating directly with discovery phases to identify ambiguity, generate probing questions, and systematically log the resolutions for engineering specifications.