vague

Clarify ambiguous requests by proposing structured, testable hypotheses.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ab180/claude-camp --skill vague-ab180
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vague
Source: https://github.com/ab180/claude-camp/tree/main/vague
Command: npx skills add https://github.com/ab180/claude-camp --skill vague-ab180

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague or ambiguous requirements into precise, actionable specifications through hypothesis-driven questioning. ALWAYS use the AskUserQuestion tool — never ask clarifying questions in plain text.

Core Features & Use Cases

  • Hypothesis-based interpretations: present plausible interpretations as options instead of open questions.
  • Phase 1: Capture and Diagnose to identify ambiguities, assumptions, and decisions.
  • Phase 2: Iterative Clarification using AskUserQuestion to resolve ambiguities with a bounded question batch.
  • Phase 3: Before/After Summary to record decisions and the clarified goal for traceability.

Quick Start

Activate vague to transform a vague requirement into a clear, testable spec by generating structured, bounded questions using the AskUserQuestion tool.

Frequently Asked Questions about vague

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

FAQPage Schema
How do I clarify vague product requirements into actionable specifications?

To clarify vague product requirements, this Skill applies hypothesis-driven questioning, presenting plausible interpretations as bounded options to transform ambiguous requests into precise, testable specifications.

What is the best way to resolve ambiguities in a feature request or bug report?

The best way to resolve ambiguities in a feature request or bug report is by generating structured, testable hypotheses through a bounded batch of 5-8 questions, rather than asking open-ended clarifications.

How does hypothesis-driven clarification work for underspecified strategy briefs?

Hypothesis-driven clarification works by diagnosing underspecified strategy briefs to identify assumptions, then proposing structured interpretations as selectable options to iteratively resolve goals and record decisions for traceability.

Can I use structured questions to manage iterative product management cycles?

Yes, you can use structured questions to manage iterative product management cycles, as the workflow bounds clarification to 5-8 questions per batch and records a before/after summary to ensure decisions are traceable.

Does this clarification workflow support traceability for product decisions?

Yes, this clarification workflow supports traceability by generating a before/after summary that records all decisions and the clarified goal, ensuring product specifications remain traceable throughout the iteration process.