Ambiguity Resolver
Turns a stakeholder's vague handed-down brief into a scoped problem statement with a named decision owner.
Testad · Fungerar
Vad den gör
For PMs who get handed a vague ask from above ('we need to do something about retention'), this skill runs a 3-stage Reframe/Scope/Action process into a fixed 'Problem Brief' output — explicit in/out-of-scope boundaries, a named decision owner, and 2-3 minimum-viable research activities with time estimates. It deliberately does not cover the PM's own vague problem (a separate drill-down handles that), only requests that originated from someone else.
Testrapport
Gave both a baseline PM and the skill the same handed-down brief ('CEO says we need to do something about retention, no detail'); only the skill's output produced an explicit out-of-scope boundary and a named decision owner — exactly the two things its description promises as its differentiator from a generic drill-down.
Testad: 2026-07-16 · Claude Code 2.x (agent harness)
Installation
git clone https://github.com/lenar-amirov/product-pipeline-public mkdir -p ~/.claude/skills cp -r product-pipeline-public/.claude/skills/ambiguity-resolver ~/.claude/skills/ambiguity-resolver
Kommandon och exempelprompter
/ambiguity-resolverTurns a stakeholder's vague handed-down brief into a scoped problem statement with a named decision owner.
Skills triggas av vanliga förfrågningar — inga kommandon att memorera. Efter installationen aktiverar prompter som dessa skillen (på engelska):
the CEO just said fix retention with zero detail, help me scope thisturn this vague executive ask into a concrete problem briefwho should own the decision on this handed-down retention project?