From pm-strategy
Turn vague briefs and half-formed opportunities into structured, actionable
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
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.
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 |
|---|---|---|
| [activity] | [time] | [insight] |
Proposed check-in: After [activity], regroup to decide whether to proceed or pivot.
npx claudepluginhub valentinbvro/pm-claude-skills --plugin pm-strategyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.