ambiguity-resolver

Featured

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

AI & Automation 1,356 stars 240 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Ambiguity Resolver Skill Turn vague briefs and half-formed opportunities into structured, actionable problem statements — so you can reply with clarity instead of asking for three more meetings. ## Required Inputs Ask the user for these if not provided: - **The vague brief or opportunity description** (even a single sentence is enough) - **Who asked for this** (stakeholder context shapes the framing) - **Known constraints** (timeline, budget, team size — if any are known) ## Three-Stage Process ### Stage 1: Reframe - Restate the vague input as 3-5 explicit questions that need answering - Identify the unstated assumptions hidden in the brief - Surface the real decision this feeds into (what will someone do differently once this is resolved?) ### Stage 2: Scope - Define what is explicitly IN scope - Define what is explicitly OUT of scope (equally important) - Identify the deadline pressure: is this urgent/important, important/not urgent, or unclear? - Name who owns the final decision and who needs to be consulted ### Stage 3: Action - Define the minimum viable research: 2-3 activities maximum that would give enough signal to move forward with confidence - Time estimate for each activity - What each activity would tell you (and what it wouldn't) - Proposed check-in point: when to regroup before committing to more **Validate** — Confirm every reframed question maps to at least one research activity. Verify scope boundaries are specific enough to say "no" to something co...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
7 months ago
Last Updated
yesterday
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

clarify

Hypothesis-based clarification pipeline that transforms ambiguous user requests into precise, actionable specifications through structured MCQ (multiple-choice questions). Classifies ambiguity into three types: vague (unclear intent), unknown (missing information), metamedium (scope/boundary undefined). Generates targeted questions per type. Auto-activates when: ambiguity score >= threshold, multi-intent conflicts detected, or user explicitly asks for clarification. Triggers: clarify, unclear, what do you mean, ambiguous, vague, specify, 명확히, 구체적으로, 뭘 원하시는지

3 Updated today
Yoodaddy0311
Web & Frontend Featured

ambiguity-detector

Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.

252 Updated 3 weeks ago
ArabelaTso
AI & Automation Listed

clarify

Use when requirements or a design are genuinely unsettled — the user asks to interrogate, sharpen, or stress-test a plan before building, or mid-build discovery surfaces a decision that materially changes the result. Do NOT use for routine changes, clear bug reports, or work whose requirements are already settled — bias to action there.

27 Updated today
KenKaiii