From pm-strategy
Structures vague briefs and ambiguous opportunities into actionable problem briefs with reframed questions, scope boundaries, and a minimum viable research plan. Useful when asked to clarify unclear requirements or define next steps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-strategy:ambiguity-resolverThe summary Claude sees in its skill listing — used to decide when to auto-load this 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.
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.
Ask the user for these if not provided:
Validate — Confirm every reframed question maps to at least one research activity. Verify scope boundaries are specific enough to say "no" to something concrete.
Restated as questions:
Unstated assumptions we should surface:
In scope: [Clear boundary] Out of scope: [Clear boundary] Decision owner: [Name/role] Timeline: [Real deadline if known, or "unclear — recommend setting one"]
Minimum viable research:
| Activity | Time required | What it tells us | What it won't tell us |
|---|---|---|---|
| [activity] | [time] | [insight] | [limitation] |
Proposed check-in: After [activity], regroup to decide whether to proceed or pivot.
Input: "We need to figure out what to do about our enterprise customers."
Restated as questions:
In scope: Enterprise accounts ($50K+ ARR) showing declining health scores in the last two quarters Out of scope: SMB segment, new enterprise acquisition strategy
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-strategyFrames product design problems before solutions exist through research synthesis, opportunity sizing, hypothesis definition, project scoping, and customer journey mapping.
Probes problems via structured questions on triggers, pains, stakes, assumptions, scope, and user requirements to ensure clarity before solutions. Activates for investigative problem discovery.
Transforms customer insights into a precise, data-backed problem statement. Use when converging on which customer problem to solve or preventing solution-first thinking.