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,228 stars 220 forks Updated today 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
5 months ago
Last Updated
today
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-before-acting

Surfaces ambiguity in one sentence and asks before acting, rather than silently picking. Use when a request supports more than one reasonable interpretation, when an external value the request does not pin down is required, when a project-specific convention must be chosen, or when an unexpected state of the world is encountered.

3 Updated today
jposluns
AI & Automation Listed

swing-clarify

Prevents premature execution on ambiguous requests. Analyzes request clarity using 5W1H decomposition, surfaces hidden assumptions, and generates structured clarifying questions before work begins. Use at the start of any non-trivial task, or when a request could be interpreted multiple ways. Triggers on "뭘 원하는건지", "요구사항 정리", "clarify", "what exactly", "scope", "requirements", "정확히 뭘", "before we start".

1 Updated today
SURFLIN2030
AI & Automation Listed

research-brief

Discovery-stage skill: turns an open product question into a structured research plan where every method is mapped to the decision it informs. Use when the user needs to plan research before acting — 'write a research plan for X', 'how should we figure out why Y happened', 'what research do we need before betting on Z', 'draft the research brief' — or when /pm routes such a request here. Do NOT use to synthesize research already run (interview-synthesizer / feedback-pattern-miner), to execute surveys or studies, for qual-vs-quant knowledge questions, or for web/market deep-research tasks.

1 Updated 5 days ago
Abhillashjadhav